Skip to main content

Gate

A control whose clearance is consumed at the moment of the act it guards. Clearance obtained at any other moment is a claim about the past, not a control on the present — so a gate is read fresh when the act happens: the head verified at merge time, custody resolved at the cleanup act, the claim state read at the move.

Estate surface​

The llm-kanban claim and move gates in kanban.py (AF-59/AF-63/ AF-66's refusal matrix); the §3 dual-review gate on merges (security gates the merge, code quality gates acceptance, CI green at the dual-bound head); AF-31's cleanup gate reading checkpoint custody at the moment of cleanup; the AF-30 round that produced the moment-of-the-act standard itself.

Relations​

  • A gate is defined by the runbook that sets the act it guards and the clearance it requires.

Notes​

A gate's objects are acts (a merge, a move, a publication), which are not concepts in this phase; a gate→act predicate is a future proposal to the format standard, not asserted here.