Signoff

Use before costly implementation to obtain independent, falsifiable PROCEED / STOP / PIVOT advice on the same decision surface. In Signoff mode, fill the generated COUNCIL.json and let ./signoff lock validate quorum, shared claims, hashes, and conflict closure.

Use after executable verification for independent read-only review of one sealed patch against one locked contract. In Signoff mode, fill review-*.json and JUDGMENT.json; ./signoff roast enforces role separation, complete criterion coverage, finding accounting, and evidence-based conflict closure.

Use for engineering work that must autonomously write a specification, obtain independent Council pressure, implement one bounded slice, prove it with executable receipts, obtain independent Roast review, and continue without goal drift or AI slop. The ./signoff state machine is authoritative.