Project
acceptance-gate
A quality gate for UI: token-only design system, Storybook, a Gherkin acceptance suite, a visual differ, and an orchestrator that lets agents open PRs overnight — never merge 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
Keep your codebase verifiable. Get your mornings back.
Open to senior frontend roles and contract work, remote across Europe. A 30-minute call on your own codebase, no slides.