304: Verification and Failure in the Fleet
How does a fleet check itself, and how do we see it failing? A node's report that its work is done is where checking starts, and the builder's word does not close the work. This chapter teaches independent verification as a method: fire on the claim, read what was built, write your own mutants against the commit and say what you did not check. It then separates agreement from corroboration, reads a fleet's failure signals from its board, and routes a retraction to every place a stale claim went.
The exercises run in pairs, one builder and one verifier, on Intent's whiteboard. They close a work package through its gate, catch four matching copies that are all wrong, read a staged fleet for its tells, and correct one claim in every place that holds it. This is the course's last chapter.
Materials
This Chapter's Insights
- ACI-068: Independent Verification
- ACI-069: Agreement Is Not Corroboration
- ACI-070: Fleet Failure & Its Signals
- ACI-071: Stale Claims
Browse every insight on the course map.