Decisions and the gate
A person decides on the evidence. The gate enforces who may, what must pass, and what always needs a person.
Deciding
The goal page says when an attempt is ready: CI green, Sigbound AI's verdict, and the done-means score. Approve lands that exact commit on the branch and writes the receipt. Send back returns it with a note. The diff is one click away; you read it when it is the question, not as the ritual.
sigbound attempt list sigbound attempt approve <number> -m "the Play section now points to Troubleshooting" sigbound attempt reject <number> -m "the third entry names the wrong Node version"
Who may decide
Whoever made the attempt cannot approve it. If a harness made it as you, you may decide it; if it made the attempt as itself, another person must. The refusal is one sentence, change_reviewer_required, and it is written to the audit log. Roles and grants say who else may decide; see Members and a repository's Access.
Branch protection
- Files that always need a person. Held paths. Any attempt touching them stops for a human even when everything else is green.
- What has to pass. Required checks by name, and whether Sigbound AI's verdict must be pass.
- Keep me honest. Rules the gate applies to you too: no self-approval, no bypass in an emergency unless break-glass is configured.
- Branches that are watched. Which branches the gate governs; pushes to others land directly and are still sealed in the ledger.
- Proposals from outside. Whether people outside the space may attempt goals, and what that costs them.
The gate's own refusals
Every refusal has a page: Gate → Refusals lists them by name, with the rule that fired. Nothing is silently dropped.