CI tools think in runs: one per merge, each an island. Pipemesh thinks in revisions: every merge moves through your pipeline job by job, so one live board always says what's deployed, what's waiting, and why. Newer work supersedes older. Jobs skip by fingerprint (files, definition, consumed artifacts), not path filters. Gates and rollbacks live in the pipeline. Jobs run on hosted runners, your own, or the GitHub Actions workflows you already have, and agents read the same state in one API call.
