Axiom

CHAPTERS is the chapter-level scope of CANONIC-CANON. Every chapter is a self-sufficient governance treatise — sourced, cited, and governed. Each chapter inherits CANONIC-CANON constraints: evidence-based, clinically grounded, governance-first.

Constraints

MUST:     Each chapter ≥ 3,000 words (NYT-quality, self-sufficient)
MUST:     Source every claim from governed scopes or cited evidence
MUST:     Follow 5-layer template (Opening, Architecture, Clinical Depth, Governance Proof, Closure)
MUST:     Use CANON voice (narrative, second-person, clinical vignettes)
MUST:     Include [B-XX], [P-XX], [G-XX] citations
MUST:     Maintain chapter ordering per CHAPTERS.md spine
MUST NOT: Fabricate clinical scenarios without evidence basis
MUST NOT: Hand-author compiled outputs

COVERAGE: 255/255

---

SPEC

Chapter List

#	File	Title	Part
00	00-FRONT-MATTER.md	Front Matter	—
01	01-THE-PROBLEM.md	The Problem	I — THE VISION
02	02-THE-INSIGHT.md	The Insight	I — THE VISION
03	03-THE-STANDARD.md	The Standard	I — THE VISION
04	04-INTEL-WHAT-YOU-KNOW.md	INTEL — What You Know	II — THE THREE PRIMITIVES
05	05-CHAT-WHAT-YOU-SAY.md	CHAT — What You Say	II — THE THREE PRIMITIVES
06	06-COIN-WHAT-YOU-EARN.md	COIN — What You Earn	II — THE THREE PRIMITIVES
07	07-THE-TRIAD.md	The TRIAD	III — THE SYSTEM
08	08-INHERITANCE.md	Inheritance	III — THE SYSTEM
09	09-THE-GALAXY.md	The GALAXY	III — THE SYSTEM
10	10-CERTIFICATION.md	Certification	III — THE SYSTEM
11	11-CODE-EVOLUTION-THEORY.md	Code Evolution Theory	IV — THE THEORY
12	12-THE-NEUTRAL-THEORY.md	The Neutral Theory of Governance Drift	IV — THE THEORY
13	13-EVOLUTIONARY-PHYLOGENETICS.md	The Governance Phylogeny	IV — THE THEORY
14	14-LEARNING-AND-EMERGENCE.md	The Learning Governance Standard	IV — THE THEORY
15	15-WHY-COMPLIANCE-FAILS.md	Why Compliance Fails	V — THE STANDARDS
16	16-HIPAA.md	HIPAA	V — THE STANDARDS
17	17-GDPR.md	GDPR	V — THE STANDARDS
18	18-SOX-AND-FINANCIAL-COMPLIANCE.md	SOX & Financial Compliance	V — THE STANDARDS
19	19-FDA-21-CFR-PART-11.md	FDA 21 CFR Part 11	V — THE STANDARDS
20	20-HITRUST-CSF.md	HITRUST CSF	V — THE STANDARDS
21	21-THE-COMPLIANCE-MATRIX.md	The Compliance Matrix	V — THE STANDARDS
22	22-MEDICINE.md	Medicine	VI — THE VERTICALS
23	23-LAW.md	Law	VI — THE VERTICALS
24	24-FINANCE.md	Finance	VI — THE VERTICALS
25	25-REAL-ESTATE.md	Real Estate	VI — THE VERTICALS
26	26-DEFENSE-AND-SECURITY.md	Defense & Security	VI — THE VERTICALS
27	27-THE-THIRTEEN-SECTORS.md	The Thirteen Sectors	VI — THE VERTICALS
28	28-COIN-WORK.md	COIN = WORK	VII — THE ECONOMICS
29	29-GRADIENT-MINTING.md	Gradient Minting	VII — THE ECONOMICS
30	30-THE-SHOP.md	The SHOP	VII — THE ECONOMICS
31	31-ENTERPRISE.md	Enterprise	VII — THE ECONOMICS
32	32-HADLEYLAB-THE-LABORATORY.md	HadleyLab — The Laboratory	VIII — THE PROOF: HADLEYLAB
33	33-MAMMOCHAT.md	MammoChat	VIII — THE PROOF: HADLEYLAB
34	34-ONCOCHAT.md	OncoChat	VIII — THE PROOF: HADLEYLAB
35	35-MEDCHAT.md	MedChat	VIII — THE PROOF: HADLEYLAB
36	36-LAWCHAT.md	LawChat	VIII — THE PROOF: HADLEYLAB
37	37-FINCHAT.md	FinChat	VIII — THE PROOF: HADLEYLAB
38	38-THE-CHAT-FLEET.md	The CHAT Fleet	VIII — THE PROOF: HADLEYLAB
39	39-ATULISMS.md	ATULISMS	VIII — THE PROOF: HADLEYLAB
40	40-THE-MOLECULAR-CLOCK.md	The Molecular Clock	VIII — THE PROOF: HADLEYLAB

---

*CHAPTERS

SPEC

CANONIC-CANON*

---

LEARNING

Evolution

Phase	Event	Evidence
Monolith	CANONIC-CANON drafted as single continuous manuscript	Initial commit, undifferentiated prose
Expansion	Grew to ~141K words across all governance domains	Word count milestones in commit history
Reindex	Split into 44 individual chapter files across 9 Parts	CHAPTERS.md spine, 00–44 file structure
Governance	Each chapter validated against 5-layer template and 3K+ floor	CANON.md constraints enforced per chapter
Closure	Added VOCAB, ROADMAP, COVERAGE, LEARNING to close scope at 255	This file and siblings

Observations

• The monolith-to-chapters transition mirrors code refactoring: same content, governed structure.
• Chapter ordering emerged from the TRIAD outward — primitives first, then system, theory, verticals, proof.
• Parts IV and VIII both address theory; the split reflects evolutionary vs. mathematical framing.
• The 9-Part structure maps cleanly to governance dimensions: each Part answers at least one.

---

*LEARNING

CHAPTERS

CANONIC-CANON*

---

ROADMAP

Later

• Track reader engagement and feedback from distribution
• Maintain chapter governance through ongoing SPEC validation
• Support future editions as new verticals and proofs emerge

---

VOCAB

Term	Definition
SCOPE	A governed unit of work. Every scope has a CANON, inherits constraints, and produces evidence.
TRIAD	The three primitives — INTEL + CHAT + COIN — that compose every governed service.
INTEL	What you know. The evidence primitive: data, models, validated knowledge.
CHAT	What you say. The interface primitive: conversation, explanation, clinical narrative.
COIN	What you earn. The economics primitive: value captured through governed work.
DIMENSION	One of eight governance questions every scope must answer (belief, proof, time, people, shape, mechanism, pattern, expression).
TIER	Governance maturity score (0–255). Measures how many dimensions a scope satisfies.
MAGIC	The validation kernel. Scans scopes, computes tiers, enforces constraints.
GALAXY	The full graph of governed scopes — every service, book, and scope connected by inheritance.
LEDGER	The immutable record of governance events — commits, validations, tier changes.
DRIFT	Uncontrolled change in a governed system. The thing governance exists to detect and correct.
GRADIENT	A measured difference between governed states. Gradients drive minting, learning, and selection.
INHERITANCE	The mechanism by which child scopes receive constraints from parent scopes.
CHAPTER	A self-sufficient governance treatise within CANONIC-CANON, sourced and cited at 3K+ words.

---

INHERITANCE CHAIN

CANONIC-CANON

CANONIC-CANON is the governor's manual. WHAT CANONIC is and WHY it matters. Governors speak idioms. INTEL + CHAT + COIN composed.

MUST:     Evidence every chapter with citations [B-XX], [P-XX], [G-XX]
MUST:     Derive every claim from governed sources (blogs, papers, governance)
MUST:     Compose INTEL — every chapter is a knowledge unit backing a contextual agent
MUST:     Speak in idioms — narrative voice drawn from blogs, not terminal
MUST:     Cover standards (HIPAA, GDPR, SOX, FDA, HITRUST) and verticals (13 sectors)
MUST:     Close with the proof — HadleyLab products ARE the evidence
MUST:     HEALTHCARE FIRST — every abstract concept gets a concrete clinical instantiation
MUST:     Anchor scenarios in MammoChat (BI-RADS), OncoChat (NCCN), MedChat (UpToDate)
MUST:     Address the enterprise healthcare buyer: CMO, CISO, compliance officer, hospital board
MUST:     Each chapter ≥ 3,000 words — NYT editorial quality, not outline
MUST NOT: Expose kernel internals (bit weights, hex values, tier boundary scores)
MUST NOT: Publish content not derivable from governed scopes
MUST NOT: Hand-author compiled outputs

BOOK

BOOK is the long-form publishing lane. Every manuscript is a PROOF artifact — authored in markdown, compiled through the MAGIC pipeline, and surfaced on the governed frontend. Deterministic. Drift-gated.

MUST:     Publish from governed inputs only — every chapter sources its claims
MUST:     Cite transcript IDFs as evidence — dev sessions (Claude, Cline, Codex) are primary source material for development narrative
MUST:     Emit proofs with every publication (author, title, chapter count, commit hash)
MUST:     Validate before deployment — build-surfaces + magic validate
MUST:     Declare domain-specific Axiom per child scope (not boilerplate)
MUST:     Declare domain-specific Constraints per child scope
MUST:     Every child instance at BOOKS/ inherits these constraints
MUST:     Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB)
MUST NOT: Nest instance directories under SERVICES/BOOK/ (service contract is the class, not the instance)
MUST:     Gate premium content via COIN — COMMUNITY reads free, BUSINESS/ENTERPRISE tiers unlock depth
MUST:     Organize chapters as individual files in CHAPTERS/ directory (NN-TITLE.md)
MUST:     Include CHAPTERS/CANON.md with chapter-level governance constraints
MUST:     Include SPINE.md declaring structural backbone (parts, chapter order, narrative arc)
MUST:     Include COMPILE.md declaring publication gate (sources, pipeline, editorial authority)
MUST:     Each chapter file ≥ 3,000 words (NYT-quality, self-sufficient)
MUST:     Chapter numbering zero-padded, kebab-case (00-PREFACE.md, 01-TITLE.md)
MUST:     All citation codes ([X-n], [W-n], [B-n], [P-n], [G-n]) resolve to BIBLIOGRAPHY.md sources on every surface (WEB, TEX, PDF)
MUST:     TEX/PDF surface renders resolved citations as endnotes or reference section — no raw markdown citation codes in output
MUST:     WEB surface renders citations as hyperlinked references to source URLs (target="_blank", never steal focus)
MUST:     Tri-view (gov | web | tex) with zero content leak between views — markdown renders as HTML on web, as LaTeX on tex, never raw
MUST NOT: Store manuscript as single monolithic file — one chapter = one file
MUST NOT: Publish private content on public surface
MUST NOT: Hand-author compiled outputs
MUST NOT: Ship boilerplate Axiom ("publishes governed content")
MUST NOT: Pass raw markdown syntax to any rendered surface — resolve or fail

SERVICES

SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.

MUST:     Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST:     Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST:     Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST:     Discover SERVICE scopes from filesystem only (no manual catalog)
MUST:     Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST:     CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST:     README.md = how to run the CANON (nothing else)
MUST:     {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST:     SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST:     VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST:     Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST:     Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST:     Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence

hadleylab-canonic

HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.

MUST:     Every app, book, paper, deal, or patent is evidence of MAGIC
MUST:     All scopes inherit canonic-canonic/CANONIC.md governance
MUST:     All users governed under USERS/ via SERVICES/USER
MUST:     Cross-index INTEL across users (INTEL.md)
MUST:     Shared events propagate to ALL affected user dashboards
MUST:     Maintain governance workspace purity (.md files only)
MUST:     Ledger all COIN (validated work) through MAGIC 255
MUST:     Compile all INTEL from governed sources
MUST:     Keep frontend/runtime implementation under ~/.canonic (hidden runtime)
MUST:     Surface governed TALK, Library, and SERVICES scopes (no orphan content)
MUST:     Derive nav labels from governed scope names (no hardcoded strings)
MUST NOT: Publish without governance (CANON.md required)
MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN
MUST NOT: Silo intelligence inside a single user when multiple are affected
MUST NOT: Expose VAULT contents outside NDA scope
MUST NOT: Store runtime artifacts in governance workspace

canonic-canonic

SPEC is governance. `canonic-canonic/` is the spec root.

MUST:     Keep this repo governance-only (.md/.pdf)
MUST:     Publish workspace mapping in CANONIC.git (no hardcoded repo lists)
MUST:     Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC
MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/)
MUST:     Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic)
MUST NOT: Embed beta-test app URLs in platform page content