Comparative analysis
This page reads the six reconstructions next to one another. It projects the book’s Chapter 6 material straight to the web, drawn from the same model, so the two surfaces cannot drift. The two convergence tables are the exact tables the print edition lays out; the correspondence matrix and the modeling-ceiling ladder carry the same data the book renders, shaped here as tables where print presents it as cards and prose. MAGE ran at none of these companies. Every mark records how the book reads an independent report against the theory, never a claim a company makes about MAGE.
Reading the tables
The convergence and ceiling tables use a small set of marks. A check means the source establishes the pattern in full. A half-circle means it establishes the pattern in part. An em-dash means the source is silent. The modeling ceiling adds a hollow circle for a representation a team exercises without naming it. The correspondence matrix keeps its words — strong, partial, and the rest — because there the word carries the reading.
Correspondence: each system against each construct
The matrix places every reconstruction against the MAGE constructs, with DocAble — the system the theory was built on — as the first row. Read down a column to see how widely one construct recurs across independent systems. Read across a row to see which arm of the theory a single system leans on.
| Case | Alignment | Modeling | Knowledge rep | Bootstrap | Conversion | Determinization | Reasoning horizon | Engineer's seat | Graduated governance |
|---|---|---|---|---|---|---|---|---|---|
| DocAble | strong | strong | strong | strong | strong | strong | strong | strong | strong |
| Cloudflare | strong | partial | strong | strong | partial | strong | strong | strong | strong |
| Spotify | strong | strong | strong | strong | partial | strong | strong | strong | partial |
| Shopify | strong | partial | partial | strong | strong | strong | strong | strong | partial |
| Docker | strong | partial | — | strong | strong | tension | strong | strong | partial |
| Siemens | strong | strong | — | strong | not-described | strong | strong | strong | not-described |
| Zenseact | strong | partial | — | strong | strong | strong | strong | strong | partial |
The modeling ceiling: how far each system’s models reach
The ladder runs from the shallowest representation a system keeps to the deepest. A system’s ceiling is the highest rung its described practice reaches. Some stop at topology and policy; others climb into behavior, invariants, and model-derived verification. The book reads the rung a source reaches, not a grade.
| Site | Service/component topology | Ownership/dependencies | Infra/environment as code | Structured policy/obligations | Data lineage | Behavioral/state models | Process/concurrency models | Scenario models | Explicit invariant registry | Model-derived verification | Bidirectional model<->code traceability | Drift gate enforcing model/code equality |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MAGE | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Cloudflare | ✓ | ✓ | ◐ | ✓ | ◐ | — | — | — | — | ◐ | — | — |
| Spotify | ✓ | ✓ | ✓ | ◐ | ✓ | — | — | — | — | ◐ | — | — |
| Shopify | ○ | ◐ | ✓ | ◐ | — | — | — | — | — | ◐ | — | — |
| Docker | ○ | ○ | ◐ | ◐ | — | — | — | — | — | — | — | — |
| Siemens | ✓ | ✓ | ◐ | ✓ | ✓ | ✓ | ◐ | ◐ | ◐ | ✓ | ✓ | — |
| Zenseact | — | ○ | ◐ | ◐ | — | — | — | — | — | — | — | — |
What every system establishes
These patterns recur across all six. Each was engineered independently, for one company’s own reasons, yet every source lands on it. Convergence this broad is the evidence that a pattern is structural rather than a house style.
| # | Pattern | Cloudflare | Spotify | Shopify | Docker | Siemens | Zenseact |
|---|---|---|---|---|---|---|---|
| U1 | Externalize knowledge | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| U2 | Act through tools | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| U3 | Bound authority | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| U4 | Probabilistic + deterministic | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| U5 | Preserve human authority | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| U6 | Engineer context | ✓ | ✓ | ✓ | ◐ | ✓ | ✓ |
| U7 | Reusable infrastructure | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| U8 | Independent evidence | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| U9 | Change the system | ◐ | ✓ | ✓ | ✓ | ◐ | ✓ |
The key names the construct each pattern instantiates and states what the source establishes.
| # | Pattern | Construct | What the source establishes |
|---|---|---|---|
| U1 | Externalize knowledge | reasoning-horizon | Autonomy needs a representation the model cannot safely rebuild each run. |
| U2 | Act through tools | alignment-principle | The sanctioned tool seam, not the prompt, is where authority is allocated. |
| U3 | Bound authority | alignment-principle | The environment, not the reasoner, sets the limit on what an agent may do. |
| U4 | Probabilistic + deterministic | determinization | Probabilistic reasoning on the ambiguous; deterministic machinery on the decidable residue. |
| U5 | Preserve human authority | engineers-seat | Humans hold intent and consequential decisions while agents scale reach. |
| U6 | Engineer context | reasoning-horizon | Curate what enters the context window; a bloated prompt degrades reasoning. |
| U7 | Reusable infrastructure | bootstrap-governance | Shared infrastructure is the environment each new agent inherits. |
| U8 | Independent evidence | alignment-principle | Generation is not evaluation, so verify the work independently. |
| U9 | Change the system | governance-conversion | When a limit appears, fix the system rather than re-prompt the agent. |
What industry is independently discovering
This second set recurs too, but the support varies from site to site. Some sources establish the pattern in full, others only in part. MAGE generalizes what these systems reach for; the gaps in a row mark where one source stops short.
| # | Pattern | Cloudflare | Spotify | Shopify | Docker | Siemens | Zenseact |
|---|---|---|---|---|---|---|---|
| G1 | Failure to improvement | ◐ | ◐ | ✓ | ✓ | — | ✓ |
| G2 | Knowledge as capital | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| G3 | Context routing | ✓ | ✓ | ✓ | ✓ | ◐ | ✓ |
| G4 | Automatic admission | ◐ | ✓ | — | — | — | ◐ |
| G5 | Compositional roles | — | ◐ | ◐ | ✓ | ✓ | ✓ |
| G6 | Model-derived targeting | ◐ | ✓ | ◐ | — | ✓ | ◐ |
The key for this bucket reads the same way.
| # | Pattern | Construct | What the source establishes |
|---|---|---|---|
| G1 | Failure to improvement | governance-conversion | A recurring loop turns each failure into a durable environmental fix. |
| G2 | Knowledge as capital | bootstrap-governance | Institutional knowledge accumulates as compounding engineering capital. |
| G3 | Context routing | reasoning-horizon | Disclose only task-relevant knowledge, on demand. |
| G4 | Automatic admission | graduated-governance | Evidence gates admit the work; review is amortized, not per-change. |
| G5 | Compositional roles | alignment-principle | Scoped specialist roles instead of one monolithic agent. |
| G6 | Model-derived targeting | modeling-principle | Act through a model of the system, not raw code. |
What none of the six generalizes
MAGE is a theory of the engineering ENVIRONMENT ITSELF as the object of engineering: everyone else engineers an agent, a runtime, a policy engine, or a model; MAGE engineers the governed environment in which commodity intelligence operates.
None of the external cases we examined describes the following machinery in the generalized form MAGE does. Not 'nobody in industry has ever done this.'
None of the reconstructions states the following machinery in the general form the theory does:
- The strongest notion of model — a Model Zoo spanning logical / behavior / process / physical / scenario / invariant / lineage / traceability views.
- Explicitly binds the model to the territory — general model<->implementation parity plus a mechanical drift check.
- A common grammar for governance mechanisms — representation / constraint / sensor / validator / gate / feedback as cross-technology types.
- Governance conversion as a general engineering operation — classify the failure, then choose the durable mechanism from model|constraint|sensor|validator|gate|interface|architecture|no-mechanism.
- Governs the accumulated governance itself — strengthen / reconcile / retire.
- Explicitly theorizes engineering capital — the compounding feedback loop as a dynamic, not just an accumulation.
- Integrates Modeling and Alignment as the two irreducible moves — better models make more obligations deterministically enforceable.
- Treats the environment itself as the object of engineering — THE SPINE (RH2), not a peer of the other seven; they are its consequences.