203: Structural Governance and Recovery
Key question: How do we keep one home for every fact, and recover when we have not?
This Chapter's ACIs
| ACI | Name | Takeaway |
|---|---|---|
| ACI-032 | The Highlander Rule | A second copy of a concern arrives before anyone notices. Ask a calibrated lookup before creating, and keep a check that goes red on a second copy. |
| ACI-033 | One Home for Every Fact | Give each fact one home and point to it from everywhere else. Write the command behind a figure, and never restate a rule. |
| ACI-034 | Namespace Archaeology | A rename is cheap in the tree and expensive wherever something keys on the name. Ask what reconciles by it first. |
| ACI-035 | Retire by Deletion | Delete the old mechanism, with its replacement in the same commit and no shim. A zero shows that nothing refers to a thing, not that nothing needs it. |
| ACI-036 | The View Is Not the Record | A rendered view is the wrong place to write or to count. Name the layer, and account for every record a migration moves. |
| ACI-037 | The Recovery Protocol | Audit by component against named rules, remediate in risk order with a gate after each phase, and end with a report on the audit. |