Project
acceptance-gate
A monorepo whose subject is its own pipeline: a visual-regression differ, a Gherkin acceptance suite, and the gate that reads them.
The problem
A numeric threshold stops being a safety net.
Once an agent can refactor thirty components in an afternoon, approving a baseline has to cost the same as reviewing a code diff — a person, in the pull request, rather than a required check nobody reads before merging.
The pipeline
The gate runs on the machine that made the commit.
Twelve processes on owned hardware cost nothing and are not rounded. The same twelve as CI jobs cost twelve minutes even when each finishes in seconds, so verification moved to the pushing machine and leaves a receipt behind it.
What is given up
A required check that never runs counts as passing.
That is written into the workflow header rather than discovered later, because it is exactly the thing branch protection would otherwise appear to be doing.
The pipeline is the part that survives a team change. A feature is a decision; a gate is the decision, enforced.
Next
Tell me what you are building.
I am interested in work where the pipeline is part of the product, and in teams that want the agents accountable to it.