304: Verification and Failure in the Fleet
Key question: How does a fleet check itself, and how do we see it failing?
This Chapter's ACIs
| ACI | Name | Takeaway |
|---|---|---|
| ACI-068 | Independent Verification | A done triggers verification. The builder's word does not close the work: a gate does, and a peer or the human signs off. Fire on the claim, read the as-built, write your own mutants, and state your coverage. |
| ACI-069 | Agreement Is Not Corroboration | Two readers who agree, or copies that match, show agreement. Corroborate with a check that could have come out the other way: the bytes, the executing tool, the real door, both sides counted, predictions first. |
| ACI-070 | Fleet Failure and Its Signals | Each fleet failure has a tell on the board: heartbeats against the clock with the human exception, message counts, double claims, resume items the tree contradicts. Give each lesson one durable home. |
| ACI-071 | Stale Claims | A corrected claim stays live wherever the correction did not reach. Route every retraction to each holder, stamp each reading with its own clock, and consolidate from the retractions. |