The reference shelf.
Seven reference groups you reach for while reading, not a sequence to read through. The glossary pins the words; the case studies show the ideas running; the rest tell you how far to trust what you just read.
Canonical glossary
Every term the book uses, defined by the responsibility it owns and by what it does not prove or authorize.
Reach for itWhen a chapter uses a word you want pinned down.Mission Control case studies
Three versioned assessments of the reference control plane — what is implemented, partial, or future, pinned to exact commits.
Reach for itWhen you want to see the ideas as running code, gaps included.Research canon
The primary sources, papers, protocols, and transcripts the book draws on, with what each one is for.
Reach for itWhen you want the source behind a claim.Coverage and maturity
What the guide covers, how strong the evidence is for each area, and what remains unproven.
Reach for itWhen deciding how much to trust a chapter's claims.Software architecture and system design
How to scope, estimate, design, operate, explain, and defend a production architecture — from core distributed systems through governed agent execution.
Reach for itBefore you have to design or defend a system.Principles to have cold
The book's one-line principles, grouped by concern, each with a plain-English gloss and the chapter that earns it.
Reach for itWhen you want the whole book in fifty lines.Mission Control operator surfaces
The eleven operational views that make authority, evidence, cost, incidents, and learning visible without creating a second source of truth.
Reach for itWhen designing or reviewing the operator experience.
11 reference documents. Chapters live in the table of contents.