A context-bounded agent cannot hold the whole system. Give it a structured, drift-checked model to reason through, and the work fits in the window.

ConceptBig idea 3 · Thesis 1

Documentation, taken to its limit, is a structured model

The apex of the documentation hierarchy is a typed model that binds docs, code, and tests A two-panel contrast. Left panel, typical agentic methods: three boxes — docs, code, and tests — stand as separate islands with no glue between them. Nothing binds them, so they drift apart and there are no guardrails; a red marker notes the missing binding. Right panel, the MAGE move: a single typed model sits at the apex and binds the same three — docs, code, and tests — with checked edges. The model is the one description the machine can check the others against, so a drift check fails the build when any of the three disagrees with it. The lesson: lift documentation to its apex, a typed model, and the three that used to drift become one checkable whole. Typical agentic methods three islands, no glue docs code tests nothing binds them → they drift no guardrails The MAGE move a typed model at the apex typed model binds intent to implementation docs code tests checked: the map must match the territory

Engineering intuition

Models used to die because keeping them current was somebody's unpaid job; agents now do that job for cents, re-checking the map against the code on every change. A drifted prose doc lies quietly — a drifted model fails the build.

Related concepts

Mechanisms

Read more

Read in the book →