Governors speak idioms. Developers speak programming. The same truth needs two languages, so we wrote two books.
Why Two
A hospital CIO walks into a board meeting and needs to explain why the institution should adopt a governance framework for its AI systems. She does not need to know how BFS traversal discovers cross-scope LEARNING or how emit_json_stable() ensures idempotent builds. She needs to know what governance means for compliance, for liability, for the institution’s ability to answer “who approved this output?” when the auditor asks.
A platform engineer sits down to implement that same governance framework. He does not need the board-level narrative about institutional risk. He needs to know how scopes inherit, how the ledger records mints, how the 255-bit validation gates work, and where in the build pipeline governance constraints are enforced.
Same truth. Different entry points. Two books.
The Canon
The Canon is the Governor’s Manual: 9 parts, 44 chapters. It speaks the language of institutions, compliance officers, hospital administrators, and the executives who sign procurement contracts.
| Part | Chapters | Audience |
|---|---|---|
| Vision | Founding, the problem, the promise | Board, investors, press |
| Three Primitives | INTEL, CHAT, COIN | Product managers, CIOs |
| The Dimensions | Governance structure | Compliance officers |
| The Proof | Evidence, validation, audit | Regulators, legal counsel |
| The Fleet | Products, services, capabilities | Buyers, evaluators |
| The Economics | COIN, pricing, Foundation tier | CFOs, procurement |
| The Evidence | Clinical trials, publications, patents | Scientists, grant reviewers |
| The Future | Roadmap, partnerships, expansion | Investors, strategic partners |
| Closure | Summary, commitments, contact | Everyone |
Every chapter is a knowledge unit. A compliance officer can read Part IV (The Proof) without reading Parts I through III. An investor can read Part II (Three Primitives) and Part VI (The Economics) and understand the business model without the technical architecture. The Canon is designed for selective reading, because executives do not read books cover to cover; they read the chapter that answers their question.
The Doctrine
The Doctrine is the Developer’s Manual: 8 parts, 48 chapters. It speaks the language of engineers, architects, and the implementers who build governed systems.
| Part | Chapters | Audience |
|---|---|---|
| Foundations | Architecture, constraints, primitives | Engineers, architects |
| Building | Scopes, inheritance, compilation | Backend developers |
| The Services | 14 core services, 79 galaxy-discoverable | Full-stack developers |
| INTEL Compilation | Graph traversal, BFS, budget functions | Compiler engineers |
| Surface | Frontend, rendering, visualization | Frontend developers |
| Economics | COIN implementation, ledger, validation | Fintech engineers |
| Closure | Testing, deployment, operations | DevOps, SRE |
| Toolchain | Build pipeline, phases, DAG orchestration | Build engineers |
The Doctrine does not repeat the Canon’s narrative. It references it. When the Canon says “every claim is sourced,” the Doctrine shows the code path: INTEL.md → CANON.json compilation → systemPrompt injection → response validation → ledger mint. When the Canon says “255-bit compliance,” the Doctrine specifies the eight dimensions, the bit allocation per dimension, and the validation gates in the build pipeline.
The Rebuild
Both books were scrapped and rebuilt from scratch on February 26, 2026. The original versions had grown organically alongside the platform, accumulating chapters that reflected the order of discovery rather than the order of understanding. The rebuild imposed a single architectural principle: every chapter is a knowledge unit, INTEL-first, where the governed intelligence precedes the narrative.
This means every chapter can be compiled independently. The CANONIC build pipeline can extract a chapter, validate its claims against the governed evidence sources, and surface it as a standalone document. A hospital CIO can receive Chapter 12 (The Fleet) as a product brief. A grant reviewer can receive Chapter 31 (The Evidence) as a capabilities summary. The books are not monoliths; they are governed knowledge bases that happen to read linearly.
Both Arrive at 255
The Canon explains what 255 means for an institution. The Doctrine explains how 255 is computed in the build pipeline. The number is the same. The understanding is different. And that is the point: governance is not a technical problem that needs a technical book, and it is not a business problem that needs a business book. It is both, simultaneously, and the two books make that duality explicit.
A procurement committee reads the Canon and understands the compliance commitment. An engineering team reads the Doctrine and understands the implementation path. When both groups arrive at the same number, the conversation shifts from “should we adopt this?” to “when do we deploy?”
Figures
| Context | Type | Data |
|---|---|---|
| post | balance | left: Canon (44 chapters), right: Doctrine (48 chapters), tilt: 0 |
Sources
| Source | Reference |
|---|---|
| CANONIC Canon | canonic-canonic/CANONIC-CANON/SPINE.md — 9 parts, 44 chapters |
| CANONIC Doctrine | canonic-canonic/CANONIC-DOCTRINE/SPINE.md — 8 parts, 48 chapters |
| BOOK service | hadleylab-canonic/SERVICES/BOOK/CANON.md |
| CANONIC | canonic.org |
| Hadley Lab | hadleylab.org |
| *BLOG | BOOKS | TWO BOOKS. ONE SYSTEM. EVERY CHAPTER GOVERNED. | 2026-02-27* |