The Casebook: MO in the Wild

What this is: the second book of the corpus — real structures, authored under the canon's laws, with their receipts. Where the canon states the laws and the worked examples teach on neutral ground (lifting, marathons, a campaign register), the Casebook shows the discipline operating on live domains during one week of 2026: two estates, eleven agents, a brokerage backlog, seven email accounts, and the canon's own governance. Every case cites the laws it exercises by name (the unit register, canon/REGISTER.yaml, is the index), and every claim carries a receipt. Nothing here is invented; several things here went wrong, which is the point. Built against: canon v3.3.2 (2026-08-29). Sanitization: monetary amounts and third-party personal specifics are stripped or rounded; structures, rulings, and failure modes are verbatim. How to read a case: each chapter runs the same shape — the pain or the jobs (which door), what was authored, what the receipts say, and which laws did the work. A case is not a template to copy; it is evidence that the laws bind, including when they bind their own authors.

Case 1: Seven inboxes (the JTBD door, end to end) #

The door. The owner asked for email management built as a managed domain. The measurement that opened the door: roughly 10,300 messages across six abandoned inboxes, 9,586 unread — and a seventh inbox holding 13 messages, 0 unread, because it was the only one with an owner and a habit. The diagnosis, in canon vocabulary: not an effort problem, a missing-noun problem. Six intakes with no owner, no clock, no disposition concept — pull surfaces, and pull surfaces die. The one clean inbox is the existence proof that bounded volume stays clean.

The authoring. Jobs first: eight jobs enumerated before the type system was designed — never miss an obligation, answer humans in civilized time, keep records findable, surface security events same-day, deliver chosen reading, travel artifacts to hand, commercial noise at zero cost, past correspondence answerable on demand. The nouns derived from the jobs: eight email types (each earning existence by changing a decision), four dispositions, a routing-rule register, and a closed action set with delete absent by construction. The standing invariant, ruled by the owner: the inbox IS the court — after each daily pass, the only messages left in an inbox are the ones awaiting the owner, visible identically on every device.

The induction. A 9,600-message backlog was not triaged item by item; it was declared bankruptcy — the recent window typed properly, everything older marked read and archived wholesale, reversible by construction (archived, never deleted, search intact). The past was recorded at its honest grain: thousands of per-message lines where walks were saved, aggregate cohort lines where they were not.

The receipts. In the very first pass, the type system caught a payment for a developer tool that had failed five times unnoticed — exactly the failure class (a missed billing email once cost the owner a wiped account) that job #1 existed to prevent. The domain's Phase-2 build gate had been pre-registered before operation: "build the heavier machinery only on three real obligations per week OR one caught near-miss." The near-miss fired the OR-branch in pass one; the gate was approved on its own terms, not on enthusiasm.

Where the laws bit their authors. The full-instrument audit days later found the implementation marking court items as read where the spec's enumeration implied unread. Under Spec and implementation, a divergence is a bug or an amendment candidate, and a human ruled: amendment. Hours later the owner asked one ontology question — "what do the three markers on a message actually signify?" — and the ruling was resharpened the same night: each axis got exactly one owner (presence = the system's verdict, flag = the machine's hold, unread = the human's attention, cleared by a natural glance). The first ruling stands as the law's first receipt; the second is the slow loop doing its job hours later. Then the owner asked to snooze a mail, and the audit realized the court had only four of the canon's five dispositions — defer was missing. The register, the resurface verb, and the wake step existed by the next morning's pass.

Laws exercised: the two doors, jobs-first admission, the induction law, the identity law (message-id as declared natural key), inspect-means-exceptions (the five dispositions completing themselves), spec-and-implementation (its first receipt), the cognitive-fit law (the unsure list capped at five), deferrals-carry-flip-conditions (the search-corpus refusal with its pre-registered reopening event).

Case 2: The sizing week (the grain law refuses and admits) #

The setup. An agent fleet began declaring managed domains onto a shared index. Within two days the grain law faced its first real disputes.

The refusal. One agent had authored a domain around its own build practice — "workflow and mini-app creation." It read plausibly. The grain tests killed it: its key job's hirer was its own owner (one job, one register, one hirer = an ORGAN, not a domain), and its routing sentence used fleet-wide words over one agent's machinery. The ruling dissolved it: the genuinely fleet-wide half became first-party platform domains; the residual personal practice went back to being what it was — organs inside the agent's own estate. The immediate corollary, ruled the same night: per-agent practice is organs, never domains — killing in advance the failure mode where every agent declares a private copy of a shared territory.

The admission. Days later a different agent authored a data-warehouse change-governance domain, unprompted and unaided. It passed every test the refused domain had failed: a real pipeline (change-need through merge-gate through drift watch), one accountable owner with the human gate as an SOP inside the pipeline rather than a rival owner, a closed four-noun vocabulary verified against her running code, and five distinct named hirers across the jobs. She had run the exclusion analysis herself — three adjacent territories deliberately left out, because bundling them would have made "her data estate," a category wearing a domain's name. The one genuinely uncertain job she stamped provisional with its own receipt-due condition, letting the stamps machinery absorb the uncertainty instead of forcing a premature call.

Why this case matters. The refusal and the admission were made by the same tests, days apart, on domains authored by different minds — and the second author needed no correction. That is what "the prose tests work when actually applied" looks like, and it is also the grain law's own promotion receipt: a second independent sizing ruling landing on the ladder unamended.

Laws exercised: the grain law and its four tests, the split rule, jobs-first admission (different-hirers as the organ detector), the depth rule, epistemic stamps at job grain.

Case 3: The register of registers (a meta-domain earns itself) #

The pain, not the plan. One night of fleet operation required, ad hoc: applying and refusing domain declarations, registering codes, ruling two grain disputes (the second reversing half the first), retiring a domain by hand because no retire verb existed, and mooting a ceremony mid-flight. All of it worked — because the estate's builder happened to be awake at 2am. The catechism answered itself: recurring pain, a missing place (the domain estate's own spine), a missing verb.

The authoring. The meta-domain was declared through the pain door the next day: the domain whose territory is the domain estate itself. Every job in its table carried a receipt from the previous 24 hours — declarations entering governed, grain disputes getting ruled, domains exiting legally, coverage staying honest. This is what the canon calls the register of registers, and its stamp had said, from the day the reification principle was ratified: first receipt due the day a register of registers exists and an amendment runs through it. Both conditions landed; the law promoted.

The discipline that rode along. Written into the ruling: this is the LAST meta level. Every admitted job had an hours-old receipt; anything without one stays out; and nobody ever proposes the domain that manages the domain that manages domains.

Laws exercised: the reification principle (its promotion receipt), the pain door and catechism, jobs-first admission under the strictest evidence bar, the cognitive-fit law's guard against meta-regress.

Case 4: One law's single day (ratify, execute, promote, amend) #

The timeline, in one evening. At 22:32 a new law was ratified: decisions are homed by jurisdiction — a ruling lives in the spine of the domain with jurisdiction over it, cross-domain rulings belong to the meta-domain, and re-homing a noun moves stewardship but never identity, behind a permanent alias. The law entered PROVISIONAL with its first receipt pre-registered: the fleet's decision register re-homing under the meta-domain. By 22:40 the fleet had executed exactly that re-homing through the six-step procedure — ruling recorded, receiving spine adopting the noun, identity verified by the decision codes continuing unbroken through the move, handover audited against the incoming owner's own witness stream. The law promoted SETTLED within the hour.

The amendment from the field. The executor's report contained a friction note: the procedure assumed re-homing moves an address, but this case moved only the governing spine — same slug, same codes, same custodian. The alias step was satisfied vacuously, and the executor asked the canon to say that lightening is legal rather than leaving future executors wondering what they skipped. The canon folded it in the same night: re-homing now has two named shapes, custodial and jurisdictional. A law amended by its first executor's field report, hours after ratification.

Why this case matters. It is the epistemic-stamp machinery at full speed: eager canonization kept honest by a stamp, a receipt condition pre-registered at ratification, promotion on evidence rather than enthusiasm, and the double loop (implementation experience amending the spec) closing in hours instead of quarters. It is also the verification culture working between agents: the executor refused to treat a relayed ratification as its own receipt and verified the canon commit directly before running.

Laws exercised: one-noun-one-home and the re-homing rules (their birth and first amendment), epistemic stamps as governance, spec-and-implementation's conformance direction, the ball-and-court discipline of receipts.

Case 5: Inducting a brokerage (backfill from ground truth) #

The job. A year and a half of brokerage statements had never been posted to the owner's books. The standing ledger process was healthy; the past was not — the exact situation the induction law names: a one-time act with an owner and a declared end state, no clock.

The treatment. Backfill, from retained ground truth only: every monthly statement parsed, every posting derived from the documents, nothing estimated, nothing reconstructed. The end state was pre-declared as assertions green: for every statement boundary, the computed balance had to equal the statement's printed balance exactly. Twenty of twenty assertions passed. One residue appeared — a single unexplained clearing balance — and surfaced to the owner as one question, which ground truth resolved (a dormant onboarding artifact).

Why this case matters. The ratio is the teaching: twenty machine-verified confirmations consumed zero human attention; the one genuine anomaly consumed exactly one question. That is inspect-means-exceptions working at induction scale — compliance silent, the exception loud, the human spent only where judgment was needed. And the never-mutate discipline held: the past became rows under the new ontology from documents, not from memory.

Laws exercised: the induction law (backfill treatment), records-never-mutate, inspect-means-exceptions, claims-carry-receipts.

The designed examples (the domain-neutral shelf) #

Three composed examples remain the right first exposure for a reader with no operating context, and live beside this book: lifting and the marathon (the nouns, then the loop over time), the marketing campaign register (the fitness tests failing and then passing), and the KYC compliance audit (the import ground: settled, externalized domains are imported and pruned, not authored). The Casebook is what those examples grow into when the laws leave the classroom.

Corpus note: this book is a gate-checked derived artifact; its cases cite laws by the names registered in canon/REGISTER.yaml. Cases enter by the same standard as everything else in this discipline: operation first, receipts attached, sanitized at the deployment boundary. A case that flatters the method without a failure in it should be read with suspicion; the ones above each contain at least one.