Axiom

PLAYBOOKS governs operational procedures. Every playbook validated.

Constraints

MUST:     Validate every playbook against governance
MUST:     Source from governed inputs only
MUST:     Version every change
MUST NOT: Hardcode implementation details in law
MUST NOT: Hand-author compiled outputs

Capabilities

GOVERNED_SOURCE, PLAYBOOK_VALIDATE, VERSION_TRACK

COVERAGE: 255/255

SPEC

Purpose

PLAYBOOKS governs operational procedures and contributor workflows.

Every playbook is a governed artifact — a deterministic procedure generated from LEARNING/BOUNDARY inputs with scope filters and identity mapping. PLAYBOOKS provides repeatable operational recipes for onboarding, deployment, compliance, and contributor coordination.

Structure

Leaf SERVICE scope. No governed child scopes. Playbook content is generated from governed LEARNING and BOUNDARY inputs.

Required closure artifacts per scope: CANON.md, README.md, PLAYBOOKS.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/PLAYBOOKS/
magic:       magic://hadleylab.org/SERVICES/PLAYBOOKS/

Generation Contract

1. Source: governed LEARNING.md and BOUNDARY inputs across fleet
2. Filter: scope-level and identity-level selection rules
3. Compile: deterministic markdown playbook per procedure
4. Output: contributor-facing operational recipes
5. Gate: CANON constraints validated before publication
6. Ledger: generation events logged with source scope references

Ecosystem Connectivity

1. Upstream: SERVICES governance contracts and LEDGER-CONSUMERS.md gate rules.
2. Runtime: governed playbook generation pipelines and deterministic outputs.
3. Frontend: governed contributor playbook surfaces when published.
4. Ledger plane: consumes governed LEARNING/BOUNDARY inputs with scope filters and identity mapping.

Pages

Default: Overview.

INTEL

Playbook Categories

Onboarding Pipeline

vault onboard --name "First Last" [--referrer USER] [--linkedin slug] [--email addr] [--skip-scan]

Name in → governed + economic user out. No manual data entry.

SOP Registry

Generation Contract

Risk Assessment

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