The specification IS the product. If it runs, it is compliant. If it is not compliant, it does not run. There are no external auditors. The system is the audit.

Dexter Hadley, MD/PhD ¹ Founder, CANONIC February 23, 2026

Abstract

CANONIC is a self-enforcing governance protocol for compliant service composition. Three primitives — INTEL, CHAT, COIN — compose into six services, governed by three pillars, validated across eight binary dimensions. The framework compiles itself before it compiles anything else: score 255 or reject. This paper formalizes the CANONIC specification: primitives, services, pillars, tiers, stages, and the self-referential publishing pipeline. Compliance is not bolted on — it is the infrastructure.

Table of Contents

1. The Protocol
2. Three Primitives
3. Six Services
4. Three Pillars
5. Tier Algebra
6. Self-Enforcement
7. The Publishing Pipeline
8. Economics
9. The GALAXY
10. What We Learned

Appendix A: Tier Algebra Proofs Appendix B: Service Composition Matrix Appendix C: References

1. The Protocol

The CANONIC spec is a single object. Everything inside the braces is compliant. Everything outside does not run.

SPEC = {
    primitives: {INTEL, CHAT, COIN}
    services:   {LEARNING, TALK, SHOP, LEDGER, VAULT, WALLET}
    pillars:    {COMPLIANCE, GALAXY, SURFACE}
    tiers:      {COMMUNITY, BUSINESS, ENTERPRISE, AGENT, MAGIC}
    stages:     {nda, work, shop, coin, close}
    workflows:  {collab, deal, contract}
}

graph LR
    subgraph "SPEC = SCOPE"
        P["Primitives<br/>INTEL · CHAT · COIN"]
        SV["Services<br/>LEARNING · TALK · SHOP<br/>LEDGER · VAULT · WALLET"]
        PI["Pillars<br/>COMPLIANCE · GALAXY · SURFACE"]
        T["Tiers<br/>COMMUNITY → BUSINESS<br/>→ ENTERPRISE → AGENT → MAGIC"]
    end

    P --> SV --> PI --> T

Source: canonic-canonic/MAGIC/CANON.md ²

SPEC = {SCOPE}. The scope is its own specification ³. There is nothing outside the braces to speculate on. If it compiles, it is governed. If it does not compile, it does not ship.

1.1 Stages — Deal Scope

Every relationship moves through five stages. The stages are ordered and irreversible — a deal cannot move backward.

1.2 Workflows — Work Scope

Three workflows map to three tiers. Each workflow composes a subset of services — higher tiers unlock more services ².

2. Three Primitives

Every CANONIC service composes from three primitives. Primitives are irreducible — they cannot be decomposed further. Services compose them; they never duplicate ².

graph TD
    INTEL["INTEL<br/>━━━━━━━━━<br/>KNOW<br/>The orchestrator"]
    CHAT["CHAT<br/>━━━━━━━━━<br/>SAY<br/>Industry voice"]
    COIN["COIN<br/>━━━━━━━━━<br/>EARN<br/>Work receipt"]

    INTEL --> CHAT
    INTEL --> COIN
    CHAT --> COIN

    style INTEL fill:#f7931a,color:#fff,font-weight:bold
    style CHAT fill:#4a90d9,color:#fff,font-weight:bold
    style COIN fill:#2ecc71,color:#fff,font-weight:bold

Source: canonic-canonic/MAGIC/SURFACE/ primitive declarations ²

INTEL is first. CHAT wires INTEL — it cannot speak without evidence ⁴. COIN wires both — you cannot earn without knowledge and speech. The dependency chain is strict: INTEL → CHAT → COIN.

3. Six Services

Six composable services. Each composes primitives — never duplicates them. Services compose into workflows. Workflows compose into tiers.

Source: canonic-canonic/MAGIC/SURFACE/SERVICES/ ²

3.1 LEARNING — Governed Accumulation

LEARNING is the accumulation lane for INTEL. Patterns, deltas, decisions — the artifacts of governed experience. LEARNING.md rotates at epoch boundaries: frozen epochs become LEARNING-{EPOCH}.md. The archive is append-only. Nothing is deleted ².

3.2 TALK — Governed Speech

TALK = CHAT + INTEL. Every word is grounded. Every claim is evidenced. CHAT never speaks without INTEL — that constraint is structural, not advisory ⁴. Industry is the only variable: FINCHAT, LAWCHAT, MAMMOCHAT, ONCOCHAT. The governance is identical; the voice changes.

3.3 SHOP — Public Projection

SHOP discovers {USER}/**/SHOP.md files. Products are discoverable. Prices are in COIN. The public surface of governed commerce.

3.4 LEDGER — Verifiable Chain

The LEDGER is an append-only chain of WORK ⁵. Each record: id (hash), prev (hash), ts (nanoseconds), type (GRADIENT), key (domain/repo/scope), from_bits / to_bits (0..255), gradient (delta), inventor (actor label) ². The LEDGER is not speculative — it is a verifiable receipt of governance work performed.

3.5 VAULT — Private Projection

VAULT discovers SERVICES/**/VAULT.md files. Auth-gated. Per-actor balances, scope flow, reserves. The private surface of governed state.

3.6 WALLET — Per-USER Container

Each USER has a WALLET. Events: MINT:WORK (validated work creates COIN), MINT:SIGNUP (500 COIN bonus), MINT:PYRAMID (500 COIN to referrer), TRANSFER (USER to USER), SPEND (pay for SHOP product), SETTLE (COIN exits to fiat via Stripe), CLOSE (epoch snapshot) ².

4. Three Pillars

MAGIC governs through three pillars. Each pillar governs a distinct surface of the protocol:

graph LR
    MAGIC["MAGIC<br/>━━━━━━━━━<br/>255 bits"]

    C["COMPLIANCE<br/>tier algebra"]
    G["GALAXY<br/>federation identity"]
    S["SURFACE<br/>platform lanes"]

    MAGIC --> C
    MAGIC --> G
    MAGIC --> S

    style MAGIC fill:#f7931a,color:#fff,font-weight:bold

Source: canonic-canonic/MAGIC/CANON.md pillar declarations ²

COMPLIANCE defines what you can do. GALAXY defines who you are. SURFACE defines where you ship. The three are orthogonal — changing one does not change the others.

5. Tier Algebra

Tiers compose monotonically. Higher tiers include all constraints of lower tiers. Adding a dimension can only increase the tier. Removing one can only decrease it. There are no shortcuts ³.

5.1 Tier Definitions

FOUNDATION = ENTERPRISE at level 3, but open canon. Non-profit equals enterprise equals open equals free. The governance is identical; the access model differs ³.

Tier inheritance is cumulative — each tier is a strict superset of the tier below ².

5.2 Tier Composition

Each tier composes a subset of eight governance dimensions. Tiers are cumulative — higher tiers include all dimensions of lower tiers plus additional requirements.

At MAGIC, all eight dimensions are satisfied. At anything less, the system identifies which dimensions are missing and reports the gap. The score is diagnostic, not decorative.

5.3 The Eight Dimensions

Source: canonic-canonic/MAGIC/COMPLIANCE/ tier algebra ²

6. Self-Enforcement

The framework validates compliance with itself. If it runs, it is compliant. If it is not compliant, it does not run. There are no external auditors. The system IS the audit ³.

Compliance state is binary:

• COMPLIANT — all eight dimensions satisfied, score = 255
• ATTENTION NEEDED — partial compliance, some dimensions missing
• NON-COMPLIANT — framework rejects execution

The self-referential property is the critical innovation: CANONIC governs itself before it governs others ⁴. The kernel compiles in O(1) time, scores 255, and proves its own compliance. This is not a consulting engagement that prescribes what it does not practice. This is a system that runs on itself.

7. The Publishing Pipeline

The spec distributes itself through three content lanes, each advertising the next:

BLOG  → accumulates  → speculation   → COMMUNITY  → FREE
PAPER → versions     → specification → BUSINESS   → $100/yr
BOOK  → emerges      → canon         → ENTERPRISE → CONTRACT

The content IS the funnel ⁶. A blog post introduces a concept (speculation). A paper formalizes it (specification). A book canonizes it (enterprise doctrine). Each stage is governed by the same 255-bit framework — the publishing pipeline is self-referential.

The pipeline is evidenced. Seven papers at 255 govern the intellectual foundation ^34678910. Blog posts advertise. The CANONIC CANON ³ is the book emerging from the papers. Everything feeds forward.

8. Economics

COIN = WORK. Every dollar spent is a governance action. Every governance action is work. The economics and the product are the same thing ⁴.

Speculation ≠ Specification. When SPEC = {SCOPE}, there is nothing to speculate on. The value is the compliance. The compliance is the product. COIN is not a speculative token — it is a verifiable work receipt minted on an immutable, append-only ledger ⁶.

8.1 The COIN Lifecycle

graph LR
    WORK["WORK<br/>validated governance action"]
    MINT["MINT<br/>COIN created"]
    WALLET["WALLET<br/>per-USER balance"]
    SPEND["SPEND<br/>SHOP purchase"]
    SETTLE["SETTLE<br/>fiat exit via Stripe"]

    WORK --> MINT --> WALLET
    WALLET --> SPEND
    WALLET --> SETTLE

    style WORK fill:#f7931a,color:#fff,font-weight:bold
    style MINT fill:#2ecc71,color:#fff,font-weight:bold

Source: canonic-canonic/MAGIC/SURFACE/SERVICES/ECON.md ²

COIN enters via MINT, moves via TRANSFER, exits via SPEND or SETTLE ¹¹. The cycle is closed. Every COIN traces back to a governance action. Every governance action traces back to WORK. There is nothing else.

8.2 MINT Events

8.3 Exit Events

9. The GALAXY

The GALAXY is the federation identity model where compliant services compose ⁹. ORGs are stars. USERs are planets. Identity boundaries are first-class — they never collapse ².

9.1 Two Fleets

Source: HTTP.json 2-fleet contract ²

9.2 ORG Topology

Sixteen ORGs across five roles ⁹:

9.3 Identity Boundaries

ORG and USER projections never collapse ². Each maintains its own governance scope:

• ORG = container (GitHub organization)
• USER = repo (github.com/{org}/{user})
• Duplicate users across ORGs is a feature (fleet mechanism)
• Signature chain: ORG root key → USER key → artifact/action
• KEY revocation supported at both levels

All surfaces — WEB (.io), iOS (native), Android (native), magic:// — meet the same 255-bit governance gate. No surface can bypass signature or governance.

10. What We Learned

The original whitepaper described six services — PITCH, TALK, DEAL, TIME, SHOP, VIA — and a MAGICVERSE of three views. That was the state of knowledge in early February 2026.

Three things changed:

1. Primitives are more fundamental than services. Services are compositions of primitives. The original spec described services directly. The current spec describes three primitives (INTEL, CHAT, COIN) and derives six services from their composition. This is a depth gain — moving from the phenotype to the genotype ⁸.

2. Pillars structure the governance surface. COMPLIANCE, GALAXY, and SURFACE are orthogonal governance surfaces. The original spec folded all governance into a flat SPEC object. The current spec separates what you can do (COMPLIANCE), who you are (GALAXY), and where you ship (SURFACE). This is the separation of concerns that makes 255-bit validation tractable.

3. The GALAXY replaced the MAGICVERSE. The MAGICVERSE was three rendering views. The GALAXY is a federation of governed organizations with identity boundaries, role-based clades, and a two-fleet architecture hardened by a mass extinction event ⁹. The model grew from a rendering abstraction to a phylogenetic system.

The spec evolves. The governance is constant. 255 or reject.

Appendix A: Tier Algebra Proofs

A.1 Monotonicity

Theorem. The tier function $T: 2^D \to {\text{COMMUNITY}, \ldots, \text{MAGIC}}$ is monotonically non-decreasing.

Proof: Let $S \subseteq S’$ be two dimension sets. Then $G(S) = \sum_{d \in S} 2^d \leq \sum_{d \in S’} 2^d = G(S’)$. Since tier thresholds are ordered, $T(S) \leq T(S’)$. $\square$

A.2 Cumulative Inclusion

Theorem. Services available at tier $T$ are a superset of services at tier $T-1$:

Proof: By tier definition, $T$ includes all constraints of $T-1$ plus additional constraints. The additional constraints unlock additional services but do not restrict existing ones. $\square$

A.3 FOUNDATION Equivalence

Theorem. FOUNDATION = ENTERPRISE at level 3 with open canon.

Proof: Both require COMMUNITY + BUSINESS + COVERAGE.md + ROADMAP.md. FOUNDATION adds canon: open constraint. ENTERPRISE adds canon: private constraint. The governance is identical; the access model differs. $\square$

Appendix B: Service Composition Matrix

B.1 Primitive Wiring

Source: canonic-canonic/MAGIC/SURFACE/SERVICES/ declarations ²

Every service that wires INTEL has governed knowledge. Every service that wires CHAT has governed speech. Every service that wires COIN has governed economics. No service duplicates a primitive. No primitive appears outside a service.

B.2 Workflow Composition

Appendix C: References

C.1 Internal Sources — CANONIC Gov Tree

C.2 External Sources

Figures

CANONIC Whitepaper | February 2026 SPEC = {SCOPE}. If it compiles, it is governed. If it does not compile, it does not ship. Source: VITAE ¹

References

1. [I-1] Author CV.

2. [I-6] The CANONIC CANON (book).

3. [I-2] MammoChat OPTS-EGO Ledger.

4. [I-3] Code Evolution Theory.

5. [X-1] Metcalf, D., Hadley, D., et al. ABC: AI, Blockchain, and Cybersecurity for Healthcare. Routledge (2024). ISBN 978-1032394558.

6. [I-4] The Neutral Theory of CANONIC Evolution.

7. [I-5] Evolutionary Phylogenetics of CANONIC.

8. [I-7] CANONIC Whitepaper v1.

9. [I-8] MammoChat to MAGIC (Blog).

10. [I-9] Why We Built This (Blog).

11. [X-2] Nakamoto, S. Bitcoin: A Peer-to-Peer Electronic Cash System (2008). https://bitcoin.org/bitcoin.pdf