CANON.md + VOCAB.md + README.md. Every scope. Every level. Three files. One truth.

The Pattern

In every governed scope in CANONIC — from the root of the organization down to a single blog post — you will find the same three files. We call them the TRIAD. They are not optional. They are not decorative. They are the minimum viable governance declaration. Without them, the scope does not compile. With them, the scope exists.

CANON.md is the declaration. It answers one question: what is this scope’s fundamental assertion? The answer is called the axiom, and it is one sentence. “PAPERS publishes governed content. Every publication evidenced.” “COIN — what you EARN. WORK = COIN.” “CLAUDE is AGENT.” One sentence that everything else derives from. If you cannot state your axiom in one sentence, you do not yet know what your scope is.

VOCAB.md is the language. It defines every term the scope uses — and only those terms. If a word appears in the scope’s governance files but not in VOCAB.md, it is undefined. Undefined terms are type errors. VOCAB.md is the type system of governance. It enforces precision where ambiguity would otherwise hide.

README.md is the interface. It tells the outside world what this scope does, how to use it, and what it exposes. README.md is the header file — the public API of governance. Other scopes that depend on yours will read README.md to understand the contract.

Why Three

The three files cover three fundamental concerns:

Identity (CANON.md) — What am I? Language (VOCAB.md) — What do my words mean? Interface (README.md) — What do I offer the world?

Every governed entity must answer all three. A scope that knows what it is but cannot define its terms is incoherent. A scope that defines its terms but has no public interface is invisible. A scope that has a public interface but no identity is a facade.

The TRIAD is the minimum. You can add more — COVERAGE.md, EVOLUTION.md, LEARNING.md — but you cannot have less. Three files is the floor. Below the floor, the compiler returns zero.

The Recursive Property

The TRIAD is recursive. It appears at every level of the governance tree:

The organization has CANON.md, VOCAB.md, README.md. Each team within the organization has CANON.md, VOCAB.md, README.md. Each project within each team has CANON.md, VOCAB.md, README.md. Each service within each project has CANON.md, VOCAB.md, README.md. Each paper, book, or blog post has (or inherits) these files.

This recursion is not bureaucracy. It is fractal governance. The same pattern at every scale means the same tools work at every scale. The validator that checks a 16-organization federation also checks a single blog post. The governance compiler does not distinguish between scopes by size. It distinguishes by compliance. 255 is 255, whether the scope is a multinational enterprise or a README.

The Axiom Is the Seed

New users often struggle with CANON.md. “What is my axiom?” they ask. “How do I know if it is right?”

The axiom is the seed of governance. It is not a description of what the scope does (that goes in README.md). It is not a definition of terms (that goes in VOCAB.md). It is the fundamental assertion — the claim from which all governance decisions derive.

Good axioms are declarative, specific, and testable:

• “WALLET stores COIN for every USER. Every event signed.” — declarative (stores), specific (COIN, USER), testable (signed events).
• “PAPERS publishes governed content. Every publication evidenced.” — declarative (publishes), specific (governed content), testable (evidenced).
• “COIN — what you EARN. WORK = COIN. Every action minted. Every mint ledgered.” — declarative (earn), specific (WORK = COIN), testable (minted, ledgered).

Bad axioms are vague, aspirational, or circular:

• “This scope does good governance.” — vague. What is “good”?
• “We aim to be compliant.” — aspirational. Aims are not axioms.
• “This scope is a scope.” — circular. Says nothing.

If you can derive your governance decisions from the axiom, the axiom is correct. If you find yourself making governance decisions that contradict the axiom, either the decision is wrong or the axiom needs revision. The axiom is the root of the logical tree. Everything branches from it.

Writing Your TRIAD

Here is a concrete example. Suppose you are creating a scope for a new research paper:

CANON.md:

# GOVERNANCE-AS-COMPILATION — CANON

inherits: hadleylab-canonic/PAPERS

---

## Axiom

**Governance is compilation. The audit is obsolete.**

---

*GOVERNANCE-AS-COMPILATION | CANON | PAPERS*

VOCAB.md:

# GOVERNANCE-AS-COMPILATION — VOCAB

inherits: hadleylab-canonic/PAPERS

---

| Term | Definition |
|------|-----------|
| Governance compilation | Transforming governance files into compliance scores |
| 255-bit fitness | Full compliance across all 8 dimensions |
| Gradient | Score delta: to_bits - from_bits |
| MAGIC | The governance compiler |
| Source language | Structured Markdown governance files |
| Compilation target | 255 |

---

*GOVERNANCE-AS-COMPILATION | VOCAB | PAPERS*

README.md:

# GOVERNANCE-AS-COMPILATION — Governance as Compilation

inherits: hadleylab-canonic/PAPERS

---

GOVERNANCE-AS-COMPILATION formalizes governance as a compilation problem.
Source: governance Markdown files. Compiler: MAGIC. Target: 255.

---

*GOVERNANCE-AS-COMPILATION | README | PAPERS*

Three files. Three concerns. One truth: this scope exists, its language is defined, and its interface is public.

Commit. Validate. Score rises. COIN mints. Governance begins.

Figures