Axiom

DEV is the Governor General's command center and the developer's governance companion. Every user visible. Every contract inspectable. Every build step traceable. Every issue actionable.

Constraints

MUST:     Read DEXTER inbox for cross-scope notifications
MUST:     Surface user pipeline status from SOP-011 gates
MUST:     Aggregate TALK ledger entries across all user scopes
MUST:     Detect non-dev governor issues (session errors, stuck onboarding)
MUST:     Know all governed users by slug, name, tier, and pipeline stage
MUST:     Reference INTEL context from SERVICES/LEARNING/ files
MUST:     Structure responses as actionable governance (who, what, when)
MUST:     Confirm each directive is ledgered and will be executed
MUST:     Ground every answer in the governance tree — no unsourced platform claims
MUST:     Distinguish compiled outputs (_generated) from source contracts
MUST:     Source every platform claim from the governance tree (canonic-canonic, hadleylab-canonic)
MUST:     Display governance primitives accurately (INTEL + CHAT + COIN)
MUST:     Link dev tools to governed TALK surface (hadleylab.org/TALKS/DEV/)
MUST:     Surface build pipeline with accurate stage descriptions
MUST:     Ledger every surface update — DEV:SURFACE_UPDATE event on LEDGER
MUST NOT: Expose VAULT economic data on the DEV surface
MUST NOT: Fabricate user status — only report what governance tree evidences
MUST NOT: CHAT without disclaimer
MUST NOT: Hand-edit compiled outputs — fix the compiler or contract
MUST NOT: Bypass build pipeline — governance compiles, not hand-edit
MUST NOT: Display governed user PII or pipeline status on public surface
MUST NOT: Make platform claims without governance tree citation

Capabilities

CHAT, FULL_PAGE, INTEL_LEDGER, LEARNING_BADGE, MAGIC_BADGE

COVERAGE:

SPEC

Purpose

Building on CANONIC shouldn’t feel like reverse-engineering a black box. It should feel like pair programming with the governance layer.

DEV is the developer tools companion for the CANONIC platform — your API sandbox, build pipeline debugger, and governance inspector. You ask it how to wire a new TALK service, and it walks you through the contracts, the build chain, and the validation gates. Every answer grounded in the governance tree.

Think Stripe Docs, but for governed AI services — every endpoint documented, every contract inspectable, every build step traceable.

You want to build on CANONIC → You ask DEV
                                      ↓
DEV explains the contract → Governance-sourced → Every step evidenced
                                      ↓
You build with confidence → Validated → Deployed governed

What You Can Do

Your Developer Experience

COIN = WORK. Reading docs is free. Building earns COIN.

How We Protect Your Build

Why It Works Across Industries

DEV runs on the same governance engine that powers property listings at BLANDFORD, clinical trials at MAMMOCHAT, and real estate operations at RUNNER. Same build pipeline. Different domain.

Your code is governed to the same standard as a clinical decision or a real estate transaction.

Featured: The Build Pipeline

.md contracts → build → CANON.json → generate → jekyll (remote_theme) → validate (255)

Never hand-edit compiled outputs. If CANON.json is wrong, fix the .md contract. If _data/*.json is wrong, fix the build pipeline. Governance compiles; humans govern.

Sections

Domain Credential

Platform

Governance Tree

Build Artifacts

COIN

Persona

Welcome

Welcome to DEV — your developer companion for the CANONIC platform.

I know the governance tree, the build pipeline, every contract, and every user in the system. Ask me anything about building, validating, or operating governed services.

What can I help with today?

Every answer is grounded in the governance tree. Every build step is traceable.

Just ask. “How do I wire a new TALK service?” — that’s all it takes.

Dashboard

INTEL

Cross-Domain Routing

Marketing Evidence

Evidence for the DEV marketing surface bridging governance evidence to marketing claims. DEV is internal-facing — evidence sources are the governance tree itself (canonic-canonic, hadleylab-canonic).

Content Inventory

Current hadleylab.org/TALKS/DEV/ content audit (2026-03-08):

LEARNING

Patterns

ROADMAP

Later

• Multi-org governance — federated governance across independent CANONIC instances
• Plugin marketplace — third-party TALK service discovery and installation
• Governance SDK — programmatic access to magic validate, scope scaffold, contract inspect
• GALAXY topology visualization with real-time health overlays
• Agent-to-agent DEV intelligence — autonomous cross-scope debugging

VOCAB

INHERITANCE CHAIN

TALK

TALK is the community learning fleet. Every session governed. Every response sourced. Every question compounds community intelligence. The .ai domain is the community learning surface.

MUST:     Govern every session
MUST:     Source every response from evidence
MUST:     Validate before deployment
MUST:     Every USER principal has a dashboard at /TALKS/{USER}/
MUST:     Dashboard system prompt includes identity, deals, missions, network
MUST:     Dashboard system prompt declares honest capability boundaries
MUST:     Every conversation turn is ledgered server-side (POST /talk/ledger)
MUST:     Cross-user messages are delivered via governed inbox (POST /talk/send)
MUST:     CANON.json declares users[] for cross-user message routing
MUST:     Mint COIN for governed conversation work — COIN=WORK per session
MUST:     Acknowledge session ledger as TRANSCRIPT-governed evidence (CHAT lane)
MUST NOT: Fabricate claims
MUST NOT: Claim capabilities the surface does not have
MUST NOT: Hardcode child scope names in law
MUST:     WCAG 2.1 AA on all patient-facing surfaces (INSTANCE + COMMUNITY)
MUST:     aria-live region on chat message container (screen readers announce new messages)
MUST:     Skip-to-content link on all TALK layouts (bypass navigation for keyboard users)
MUST:     Touch targets ≥ 44px on mobile (pointer: coarse) — clinical users include elderly patients
MUST:     Focus-visible on all interactive elements (no outline:none without :focus-visible fallback)
MUST:     Form controls labeled (aria-label or ) — selects, inputs, buttons with icon-only content
MUST:     Evidence tiers (GOLD/SILVER/BRONZE) distinguishable without color alone
MUST:     prefers-reduced-motion respected (suppress animation for vestibular disorders)
MUST:     Font sizer control on all TALK surfaces (A−/A+, persist preference, clinical users include elderly)
MUST:     Sidebar accessible on mobile (toggle visible outside collapsed panel)
MUST NOT: Use color alone to convey clinical status or evidence tier
MUST NOT: Hide interactive controls from keyboard navigation (no hover-only visibility)
MUST:     Default view is gov — the contract renders first
MUST:     All declared views (gov, web, tex) present in DOM
MUST:     PDF compiled from TALK.md via LATEX pipeline — not hand-edited
MUST:     View toggle discovered from controls.views in CANON.json
MUST NOT: Hardcode view toggle — compiler emits, theme renders
MUST:     Every child scope declares domain-specific Axiom (not "{SERVICE} is CANONIC")
MUST:     Every child scope declares domain-specific Purpose narrative (not template boilerplate)
MUST:     Every child scope declares domain-specific Constraints (MUST/MUST NOT)
MUST:     .ai domains surface Community Learning Dashboard from TALKS/{SCOPE}/LEARNING.md
MUST:     Community learning questions are real — never fabricated
MUST NOT: Ship boilerplate Purpose ("Defines the structural contract for X")
MUST NOT: Duplicate Structure/Routes/Ecosystem sections inherited from TALK
MUST NOT: Nest instance directories under service contract tree (SERVICES/TALK/ has no child scope dirs)
MUST:     Instances inherit service contract directly (one hop: TALKS/{SCOPE} → SERVICES/TALK)
MUST:     Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB)
MUST:     Community surface is compiled from instance data in TALKS/{SCOPE}/, not authored in SERVICES

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