The 477:1 Problem

Every AI team celebrates when their agent catches errors. Nobody tracks whether those errors stop recurring. We ran 6 autonomous agents through 145+ specs and 960+ commits. The critical metric we discovered: 477:1 . That's 4,768 violations detected but only 18 promoted to structural enforcement. A stark gap between detection and actual prevention. What the Ratio Means A violation is a detected failure — an agent breaks rules, uses outdated context, or misses constraints. Detection is straightforward; every monitoring tool does it. A promotion is when that violation becomes structurally impossible to repeat. Not "we documented it." Not "we added a Jira ticket." The violation gets encoded as an L5 hook, L4 test, or L3 template in the enforcement ladder . The remaining 4,750 violations can recur because nothing structural changed — despite logging and alerting. Why the Gap Exists 1. No promotion pipeline. Teams have error logging but lack mechanisms to transform logged errors into structu