The failure catalog is the real value. Examples:

- "Ghost Target" (pattern #3): Agent confidently "fixed" a bug that didn't exist. Now we verify gaps before writing code. - "Write-Only Field" (pattern #8): Agent wrote data at character creation that nothing ever read at runtime. 17 fields exposed. Now every data write requires a consume-site proof chain. - "Parallel Drift" (pattern #9): Two code paths computing the same attack logic diverged by 21 modifiers. Now every resolver change requires parity verification across all paths. - "Coverage Theater" (pattern #12): 30+ rows in the coverage map went stale. Tests passed but tracked nothing. Now coverage updates are mandatory in every debrief. - "Governance Consumption Failure" (pattern #15): PM wrote rules. Nobody read them. Process docs had no enforcement mechanism. Now methodology lives in auto-loaded config, not optional docs.

21 patterns total, each with: the failure that created it, the rule that prevents it, and a real example from production.

Not a framework you install — it's a methodology repo. The patterns are language/tool agnostic.

Happy to answer questions about what it's like building real software with multi-agent coordination when you're not a developer.