Day 5: The Reckoning
Key question: What goes wrong?
Today's ACIs
| ACI | Name | Takeaway |
|---|---|---|
| ACI-010 | The Regression Cascade | A cluster of regression-fix commits in a short window is a leading indicator of architectural fragility. The agent fixes symptoms; it does not diagnose the disease. |
| ACI-023 | The Recovery Protocol | When architectural debt has accumulated, the response is structured forensic audit, not incremental fixes. Piecemeal cleanup produces more violations than it resolves. |
| ACI-004 | When Coding Succeeds But the Project Fails | Working software is not the same as a working product. The MeetZaya case study is the evidence. |
| ACI-026 | The Generation Trap | When code is cheap, the natural response is to write more of it. This is the wrong response. The scarce skill is knowing what is worth building. |
| ACI-025 | The Productivity Claim | The productivity multiplier varies by task type: 10-50x for mechanical work, 2-3x for features, 1x for architecture, less than 1x for scope-sensitive work. |