What is a human gate?
A protected action that cannot go ahead until an authorised person approves it.
A human gate sits in front of an action that is hard or impossible to undo. Agents can prepare everything up to it. They cannot pass it without a person's yes, given at the gate or in writing beforehand.
The most common one is the merge gate: work arrives as a reviewed pull request with its evidence, and a person decides whether it joins the main branch.
How many gates you need depends on the product. A low-risk internal prototype may need fewer. A product that handles money, personal data or public claims may need more.
Lessons that use it
- 14Returning at the merge gateI read the evidence, then decide what ships.
The ruleMake the thing you review small, single-purpose and tied to one exact commit.
- 27The bottleneckMe.
The rulePick the few decisions you will never hand over, write them down, and delegate the rest.
- 15What happens after the code worksWorking code starts the delivery. It does not finish it.
The ruleTreat "it works here", "it is deployed" and "it works for users" as three different claims.
- 13Anatomy of an AFK runIt starts with a contract and ends at a gate. Nothing in between merges without my yes.
The ruleDesign the run so the most it can do without you is prepare a decision, or carry out one you granted in writing before you left.