What it stores
The Registry keeps what Zevron has already proven: unit decompositions, repair patterns that fixed real failures, and attack-resistant shapes that survived the Crucible. Each entry carries a Bayesian confidence and its full attack history, so Zevron knows not just that a pattern worked, but how hard it was pushed.
How it bends the cost curve
When a new unit matches a high-confidence entry, Zevron reuses the proven shape. A registry hit that passes on the first try skips candidate generation entirely — the most expensive stage. Capability rises because proven patterns are more likely to hold; cost falls because the funnel does less work.
On a held-out benchmark, turning the registry on moved the pass-rate from 41% to 77% while cost per task fell. Turn it off and the curve goes flat.
The moat
The Registry can't be copied — it's earned, per codebase, from verified outcomes. It is why Zevron gets cheaper and better the more it runs. Run the curve to see it: capability up, cost down, registry-off flat.