THE FOUNDATION

The standard. Two languages. One target.

FOUNDATION is the specification layer — the constitution ratified before the platform operates. Two books written for two audiences: the Canon for governors who need to understand AI risk, and the Doctrine for developers who need to build compliant systems. One compliance target: 255 bits. Developed by Hadley Lab, the first organization certified to MAGIC 255.

Read the Canon Read the Doctrine
94
CHAPTERS
255
MAGIC SCORE
28
PARTNER ORGS
NCT
CLINICAL TRIAL
FOR GOVERNORS

The CANONIC Canon.

You run the organization. You sign off on AI deployments. You face the auditor. The Canon is written for you — 9 parts, 44 chapters of flowing human prose that explains what AI governance is, why it matters, and how the 255-bit compliance framework works. Every abstract concept gets a concrete clinical instantiation. Every claim sourced.

THE THEORY

Governors speak idioms. This book speaks yours.

From the problem (ungoverned AI wastes $255B a year in healthcare alone) through the solution (eight governance dimensions, five compliance tiers, one mathematical target) to the proof (MammoChat, RUNNER, and the full fleet). Kimura's neutral theory, 255-bit fitness, phylogenetic inheritance — unified into one framework a board can understand.

255 CANON
PAPER
The $255 Billion Wound
American healthcare wastes $255B a year on governance it cannot prove. The paper that quantifies the problem the Canon solves.
Read the paper →
PAPER
Governance as Compilation
The thesis. Governance is structurally isomorphic to program compilation. MAGIC is the compliance engine. 255 is the target.
Read the paper →
ESSAY
AlphaGo at 10
Ten years ago, a machine proved intuition was computable. It forgot to prove it was trustworthy.
Read the essay →
Read the Canon Talk to Us
FOR DEVELOPERS

The CANONIC Doctrine.

You write the code. You build the services. You ship the product. The Doctrine is written for you — 8 parts, 50 chapters that take you from your first CANON.md to a fully governed service at 255. DRY. MATH. FIXED. PURE. Every pattern has a working implementation.

THE MANUAL

Devs speak programming. This book speaks yours.

Your first axiom. Your first TRIAD (CANON.md + README.md + VOCAB.md = 35 bits). Your first scope. Your first service. Your first 255. FHIR to INTEL to CHAT to COIN pipeline examples. Python, Swift, TypeScript, Markdown. Clinical informatics examples throughout — because healthcare is where governance is hardest.

One platform. One target. Any domain.

Three files. 35 bits. Five minutes.

The minimum viable governance is three files — CANON.md declares what the scope is, README.md describes the public interface, VOCAB.md defines every term. This triad validates to COMMUNITY tier (35 bits). From there, add specifications, coverage, learning, and language to climb toward 255.

  • TRIAD: CANON.md + README.md + VOCAB.md = 35 bits
  • Languages: Python, Swift, TypeScript, C, Markdown
  • Pipeline: Author → Commit → Validate → Ship
Read the Doctrine

28 organizations. One inheritance tree.

The CANONIC Network is a federation — 28 organizations, each governing its own scope under the same compliance engine. The topology is ORG/USER — filesystem is the source of truth. A clinical AI organization inherits Medicine. A real estate organization inherits Real_Estate. The engine validates them identically.

  • 28 GitHub organizations
  • Federation by inheritance — not by API
  • ORG/USER topology — filesystem is truth
Read the Doctrine Talk to Us
CERTIFICATION

Eight dimensions. Five tiers. One target.

Every governed scope validates toward 255. Eight questions, eight bits, one score. Each question either has an answer or it does not. The score is a bitmask — every bit carries information.

What does this system do?
CANON.md exists. The system states what it is, what it believes, and what it will not do.
What terms does it define?
VOCAB.md exists. Every term defined. No ambiguity. No hallucination by design.
Where is it going?
ROADMAP.md exists. What shipped, what is next, and when. Versioned and public.
How is it specified?
The specification document exists. Exact interface and boundaries described.
How healthy is it?
COVERAGE.md exists. Eight diagnostic questions answered. No gaps permitted.
How is it organized?
Inheritance, constraints, and axioms enforced in code — not a policy binder.
What has it learned?
LEARNING.md exists. The system learns from its own errors. Each incident closes a gap.
What language does it speak?
DESIGN inherited. The governance language is inherited, not invented. Consistency across the entire stack.
See the full MAGIC spec See the tier system
THE EVIDENCE

Read the proof.

Hadley Lab is the first organization certified to 255. The proof fleet ships software under the same governance standard described in these books. Every claim below traces to governed evidence.

BOOK 1
The CANONIC Canon
The theory of code governance intelligence. 9 parts, 44 chapters. Governors speak idioms.
Read the book →
BOOK 2
The CANONIC Doctrine
The implementation manual. 8 parts, 50 chapters. Devs speak programming.
Read the book →
BOOK 5
The Art of the CANONIC Deal
Commerce and governance as one design. How governance creates deal flow.
Read the book →
ORIGIN
Why We Built This
The origin story. A surgeon, a hallucination, and the 14-year journey to a governance framework.
Read the story →
ORIGIN
MammoChat to MAGIC
How one mammogram changed everything. From a BI-RADS 4 finding nobody could trace to a framework that proves $7.5B in violations were preventable.
Read the essay →
PAPER
Content as Proof of Work
Bitcoin burns electricity. CANONIC publishes a book. The content is the work. The work is the COIN.
Read the paper →
All Papers All Books