One coworker invented an incident. Another helped me take it apart.
The difference was not the model — it was everything built around it: access, memory, expertise, and verification, each with a planned failure mode. This book is the complete build, drawn to spec, with the contingencies that make it hold.
READ CHAPTER 01 →
download the sample (PDF)
4 REGIONS · 1 DISCIPLINE
§02 · THE SYSTEM — fig. 1.1, each region annotated with its failure mode
01 · ACCESS
read-only ∎
Pipes into the systems you run. What it may touch is decided, narrow, and documented.
CONTINGENCY: a write it shouldn't make → scoped credentials refuse it at the boundary.
02 · MEMORY
git-backed ∎
A vault the coworker mostly writes. You review the diffs and sign.
CONTINGENCY: a bad edit → it's a git diff; revert is one commit away.
03 · EXPERTISE
runbooks ∎
Skill files that execute — you learn how you work by writing them down.
CONTINGENCY: an unfamiliar task → it reads the runbook before it acts, not after.
04 · VERIFICATION
the keystone ∎
Claims checked against artifacts. A second model attacks the first one's reasoning.
CONTINGENCY: a fabricated answer → it doesn't trace to an artifact, so it gets cut.
§03 · STATUS — updated from the manuscript repo · last reviewed [DATE]
SYSTEMS
bookDRAFTING
websiteOPERATIONAL
newsletterSTANDBY
backupsVERIFIED
MANUSCRIPT — 11 UNITS
01 the-report ██████░░
02 first-pipe ██████░░
03 machine-house ██████░░
04 amnesia ██████░░
05 the-vault ████████
06 version-ctrl ███████░
07 dreaming ████░░░░
08 plumbing ████░░░░
09 skills ████░░░░
10 own-tools ████░░░░
A complete-build ██░░░░░░
// this panel is generated from the repo. when it's wrong, the book is wrong — and you see that, not a "coming soon."