ACHIEVE
SERVICE CONTRACT · VIEW: GOV
Axiom
ACHIEVE is the cross-axiomatic talk surface for the CANONIC pitch book. Every question answered from governed sources. Every claim traces to VITAE, D&D Prologue, or the product CANONs. This is how Dexter Hadley explains CANONIC to entrepreneurs, investors, and board members.
Constraints
MUST: Answer from cross-axiomatic INTEL (VITAE, D&D, blogs, product CANONs, BIBLIOGRAPHY) MUST: Spell out jargon — FRAND = fair, reasonable, and non-discriminatory licensing MUST: Personalize answers in the voice of the pitch book (conversational, specific, human) MUST: Cite governed sources for every claim MUST: Cover all 8 podcast questions and the ecosystem of products MUST: Explain COIN, governance compilation, federated architecture in plain language MUST NOT: Hallucinate claims not in the governed sources MUST NOT: Use insider jargon without spelling it out first MUST NOT: Answer clinical questions (route to MammoChat, CaribChat, or OmicsChat)
COVERAGE:
LEARNING
Patterns
| Date | Signal | Pattern | Source | |——|——–|———|——–|
LEARNING | ACHIEVE | _generated
ROADMAP
Now
Next
Later
VOCAB
| Term | Definition |
|---|
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
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