Axiom

MAGIC enforces governance at runtime. Every request validated. Every response governed.

Constraints

MUST:     Route through governed gateway
MUST:     Validate every request against governance
MUST:     Emit telemetry to governed surfaces
MUST:     Fail closed on validation failure
MUST NOT: Hardcode credentials or provider bindings
MUST NOT: Bypass governance validation

Capabilities

FAIL_CLOSED, GATEWAY_ROUTE, REQUEST_VALIDATE, TELEMETRY_EMIT

COVERAGE: 255/255

SPEC

Purpose

MAGIC is the infrastructure service. Provider switching, governance validation, tier algebra. Every request validated. Every response governed.

MAGIC enforces 255-bit governance at runtime. It manages the LLM provider landscape (Anthropic, RunPod, Vast.ai, OpenAI), runs the BAKEOFF evaluation harness, and validates that every scope meets its tier contract. Providers are switchable — not hardcoded. Quality is measured — not assumed.

Tier Algebra

255 is the composition: all artifacts present, INTEL bridge connected, full governance.

Provider Landscape

BAKEOFF Harness

The BAKEOFF evaluates providers across latency, throughput, cost/token, and quality. Decision criteria: cost-adjusted quality per governed task. Results drive provider switching — not opinion.

Structure

Root MAGIC domains: RUNPOD/ (serverless Runpod.io LLM provider scope). VASTAI/ (Vast.ai persistent-instance LLM provider scope). BAKEOFF/ (governed provider evaluation harness).

Required closure artifacts per scope: CANON.md, README.md, {SCOPE}.md, VOCAB.md, ROADMAP.md, COVERAGE.md, LEARNING.md.

Learning lane per governed scope: LEARNING.md at the scope root is terminal and SHALL NOT nest further LEARNING/.

Routes

web_docs: https://hadleylab.org/
web_surface: https://hadleylab.org/SERVICES/MAGIC/
magic:    magic://hadleylab.org/SERVICES/MAGIC/

Ecosystem Connectivity

1. Upstream: canonic-canonic/MAGIC canonical law — the source of tier algebra and MAGIC compliance.
2. Runtime: ~/.canonic discovery/generation/relink workflows — compile-canon-json validates all.
3. TALK plane: provider switching feeds /chat — Anthropic primary, fallback chain governed.
4. LEDGER plane: tier validation results logged — fake 255 fails at the compiler.
5. Frontend: Jekyll + remote_theme (canonic-canonic/DESIGN) — governed surface rendering.

Pages

Default: Overview.

INTEL

Provider Landscape

BAKEOFF Harness

Infrastructure Stack

Tier Algebra

MAGIC (255) is the composition: all artifacts present, INTEL bridge connected, full governance.

Fleet Topology

Risk Assessment

Test

LEARNING

Patterns

ROADMAP

VOCAB

INHERITANCE CHAIN

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