A release gate only works if the merge button has to ask it. Here's how to wire one into CI so it fails closed.

In the last post, Nothing Should Merge on an AI's Word , I argued that AI-written code needs a gate between "the agent finished" and "this is a pull request," and that the gate should check evidence: a review that ran, tests that passed on this exact version, and a person who said yes.

There's a hole in that picture. A gate inside one tool only covers changes made through that tool. Pull requests still get opened by hand, branches still get pushed, and the merge button on GitHub or GitLab doesn't know your AI platform exists. If the gate can be skipped by clicking somewhere else, it's not a gate.

So the real question is: how do you make the merge itself ask for a verdict?

Put the check where the merge happens

The answer is boring, which is a good sign: a CI job that asks the gate for a verdict on this pull request, and fails when the answer is no.…