203: Structural Governance and Recovery
How do we keep one home for every fact, and recover when we have not? When an agent writes the code, a second implementation of one concern can arrive before anyone notices, and the guards attach to only one copy. This chapter teaches the one-home rule at project scale: look before you create, and keep a check that goes red on a second copy at every landing. The same rule governs documents, figures and the rule book. A rename is cheap in the tree and expensive wherever something keys on the name. A retired mechanism is deleted, with its replacement landing in the same commit or release. A rendered view is the wrong place to write or to count. And when the structure has decayed anyway, the way back is a forensic audit, remediated in risk order with a gate after each phase.
Materials
This Chapter's Insights
- ACI-032: The Highlander Rule
- ACI-033: One Home for Every Fact
- ACI-034: Namespace Archaeology
- ACI-035: Retire by Deletion
- ACI-036: The View Is Not the Record
- ACI-037: The Recovery Protocol
Browse every insight on the course map.