Appendix A — MAGE Engineering Stacks

A.6 Governance Conversion

A.6.1 The Capability

Turn recurring failures and judgments into durable engineering structure while keeping the control machinery legible. Model how controls relate, expose gaps and coupling, and convert recurring failures into new or stronger controls.

A.6.2 When This Stack Earns Its Keep

Reach for it when:

A.6.3 The Composition

The Governance-Conversion stack: model the control machinery, find its gaps, interpret a recurring failure into a durable control, update the estate, iterate A solid four-move loop. CONTROL MACHINERY is the explicit model of rules, gates, models, and sensors. Inspecting or querying it exposes GAP or IMPACT — where control is weak or coupled. When a failure recurs, INTERPRET converts the failure class into a durable control. UPDATE ESTATE folds that control back in, and a curved solid feedback returns to the control machinery for the next iteration. This is a four-move loop, not six mandatory stages: rule registries, dependency graphs, and indexes are possible implementations, not required steps. CONTROL MACHINERY rules · gates · models · sensors inspect / query GAPS / COUPLING where is control weak, stale, or entangled? recurring failure? INTERPRET failure class → durable control UPDATE ESTATE next iteration load-bearing loop (all required) Solid loop: the load-bearing composition. Four moves, not six mandatory stages.
Figure A.6-1. The governance-conversion composition, a loop. The CONTROL MACHINERY — rules, gates, models, sensors — is inspected and queried to expose GAPS / COUPLING: where control is weak, stale, or entangled. When a failure recurs there, INTERPRET converts the failure class into a durable control, and UPDATE MACHINERY folds it in; a solid feedback edge returns to the machinery for the next iteration. The four moves form the core loop.

A.6.4 Constituent Moves

Table A.6-1.
MoveRole
MODELMake the control machinery explicit — rules, gates, models, sensors.
EXPOSEQuery the machinery for gaps, staleness, and coupling.
CONVERTInterpret a recurring failure class into a new or strengthened control.
UPDATEFold the control back into the machinery; the model changes with it.

A.6.5 Why These Travel Together

As a governed environment grows, its controls overlap, depend on one another, go stale, and acquire blast radius. Eventually the control machinery itself becomes difficult to reason about. When that happens, model it explicitly.

Once the machinery is explicit, interpret recurring failures against it. A failure worth converting becomes a new or stronger mechanism, and the machinery model updates with it. This creates engineering capital: the environment changes so future work no longer depends on someone remembering the lesson. Rule registries, dependency graphs, indexes, and metadata are possible implementations.

Mechanisms: control census · control-dependency graph · governance conversion

© James C. Davis, 2026–present