Adjudicating a review

Read reference/adjudication.md — it is the protocol. In short:

1. Locate the raw claims — the most recent *.codex.json in .codex-failsafe/ (or the path the run printed). Never edit this file.
2. For each claim, run its how_to_falsify first. The failsafe itself named the command or document that would prove it wrong; that is the cheapest adjudication and was chosen by the party with no stake.
3. Assign a disposition — confirmed, refuted (evidence required), governed (citation required), out-of-scope (destination required), or open. If you cannot produce evidence against a claim, it is open, not refuted — "I disagree" is not a disposition.
4. Route what survives: a confirmed finding is a fix, plus the test or check that should have caught it, plus a sweep of its defect_class across every sibling surface — done now, not when the next pass rediscovers the same shape one file over. An open question goes to the user with the fork stated plainly.
5. Write the ledger entry beside the raw file: same stamp, .json extension — task, scope, the pass accounting, and each claim with its disposition and evidence.
6. Once in a while, read the ledger backwards for the four failure smells: everything refuted (fishing or capture), falsifications never run (capture), no decision ever moved (ceremony), most findings against code the review itself caused or second instances of a class already confirmed (the loop reviewing its own output). Tell the user which smell you see; retuning or retiring the failsafe is their call.