Gate ledger

The idea

A registry names each gate and the failure it prevents. From records, it counts how often the gate caught that failure and how often a person overruled it.

The problem
Gates are added and never questioned, though each one costs time.
Why it matters
A counted gate with no catch in 90 days becomes a removal candidate for a person to decide.
Where it stands
In production as of

Recorded evidence

  • Production · Release production check

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Rulebook mined from history

    Commits, PRs, reviews, tickets, tests, CI and code are mined into rule candidates with evidence and scope. Accepted rules become checks, tested first against past changes. A rule that catches nothing in 90 days goes to its author to retire or keep.

  • Check-before-finishing Stop hook

    In a native Claude Code round, a Stop hook that uses no model holds the round once if code changed after the last passing check. A piped or masked status does not count as a pass.

  • Stage exit checklists and loop limits

    Each stage has an exit checklist. Code judges the clear items and System One the unclear ones. Repeated holds go to a person, and a loop guard stops the run when the same result repeats.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.