why checking ≪ doing lets verification work at all; the ladder + coverage, and the three failure modes (coverage exhaustion / discrimination collapse / quantifier inversion)

Surveyed ground · 8 nodes charted

edges from the current catalog revision

The guide, on step 1: Every pattern in the Atlas stands on the same ground. An agent is a context window being spent, and this Node states the claim everything else argues from.
The guide, on step 2: Before you can lower a cost you have to price it. This Node is the price model for context itself, and every tradeoff in the Atlas is quoted in its terms.
The guide, on step 3: The price model applied. One thirty-turn session is billed, then re-billed under six single design decisions, so you can watch each law move a real total. Keep this bill in hand for the rest of the walk.
The guide, on step 4: The first mechanism. A cost you cannot delete can still be paid later or paid by someone else, and most designs in the Atlas are making one of those two moves.
The guide, on step 5: The mechanism at work. One ten-thousand-token guide is billed three ways. Moving the payment point protects the early turns, and moving the payer protects the orchestrator, even when the system as a whole spends more.
The guide, on step 6: The pay-elsewhere branch on its own. When work would flood a window that has to stay clear, hand the work a window of its own and take back only the result.
The guide, on step 7: The offload at work. A full investigation runs in a child agent while the orchestrator keeps drafting, and only the verdict comes back. Everything the investigation touched stays out of the window that mattered.
The guide, on step 8: The closing lens. Checking a result is cheaper than producing it, and every design on this walk leans on that gap. Take it back to the map with you.

Legend pattern · concept example roadmap connection tour route

Open the map