COIN

Axiom

COIN is the economic shadow of WORK. Every mint ledgered. Every burn evidenced.

Constraints

MUST:     Ledger every mint and burn
MUST:     Evidence-back every token
MUST:     Record shape: id, prev, ts, event, actor, scope, work, hash
MUST:     Supply ceiling = scopes x 255 per CLOSE epoch (work budget resets each economic period)
MUST:     Validate supply ceiling on every build (WARN on overshoot, FAIL on unsigned mints)
MUST NOT: Mint without evidence
MUST NOT: Mutate ledger history

Capabilities

BURN, EVIDENCE_BACK, LEDGER_APPEND, MINT

COVERAGE: 255/255

SPEC

INTEL

Token Architecture

Component	Implementation	Status
Mint trigger	CONTRIBUTE, TALK, PROVISION events	ACTIVE
Ledger store	Cloudflare KV (TALK_KV) — `ledger:COIN:{scope}`	ACTIVE
Chain integrity	SHA-256 content hash + prev pointer	ACTIVE
Event types	MINT:CONTRIBUTE, MINT:TALK, MINT:PROVISION, MINT:REVIEW, BURN:REDEEM	DEFINED

COIN Events

Event	Trigger	Evidence
MINT:CONTRIBUTE	Valid contribution submitted	contribution_id in LEDGER
MINT:TALK	Ledgered conversation turn	trace_id in LEDGER → TRANSCRIPT IDF: transcript://chat/{scope}/{trace_id}
MINT:PROVISION	Infrastructure provisioned	provider_record in LEDGER
MINT:REVIEW	Community review feedback incorporated into governed artifacts	review_id, evidence_ref[]	BRONZE: 32 COIN / GOLD: 64 COIN
BURN:REDEEM	Token redeemed for service	redemption_id in LEDGER

LEDGER Integration

Every COIN event MUST:

Append to ledger:COIN:{scope} via appendToLedger()
Include work_ref linking to the source event
Backpropagate to LEARNING.md as pattern row

Signal mapping:

MINT:CONTRIBUTE  → COIN_MINTED (source: contribution_id)
MINT:TALK        → COIN_MINTED (source: trace_id → transcript://chat/{scope}/{trace_id})
MINT:PROVISION   → COIN_MINTED (source: provider_record)
MINT:REVIEW      → COIN_MINTED (source: review_id, evidence_ref[])
BURN:REDEEM      → COIN_BURNED (source: redemption_id)

Risk Assessment

Risk	Severity	Mitigation
Double-mint on retry	HIGH	Idempotency key from source event hash
Mint without evidence	CRITICAL	appendToLedger() requires work_ref
Ledger overflow	LOW	Overflow rotation with epoch archiving at 1000 cap
Cross-scope mint leakage	MEDIUM	Scope-keyed ledger partitioning

Test

prompt	expect	cross
What are the COIN event types?	MINT,BURN	LEDGER
How is chain integrity maintained for COIN events?	SHA-256	LEDGER
What prevents double-mint on retry?	idempotency,hash	LEDGER
What triggers a MINT:CONTRIBUTE event?	contribution	LEDGER
Where is the COIN ledger stored?	Cloudflare KV,TALK_KV	TALK

LEARNING

Patterns

Date	Signal	Pattern	Source
2026-02-24	TRIAD_COMPLETE	COIN service scope governance completed — full MAGIC 255	CANON.md
2026-03-23	NEW_PATTERN	MINT_REVIEW_EVENT: New circulation event MINT:REVIEW defined for community review feedback. BRONZE tier (32 COIN) for informal feedback leading to governed remediation. GOLD tier (64 COIN) for structured evidence-backed line-level review. First application: ir4y + yanabeda book dedup review (BRONZE, 32 COIN each).	Community review metaclosure session
2026-03-15	TIER_DECLARATION	Every TALK scope in the Fleet table declares FREE or FREEMIUM. COIN validation gate (gate_tier_declaration) enforces. Community surfaces differentiate free education from COIN-gated professional features. Foundation tier provides enterprise at zero cost for nonprofits.	Free vs commercial differentiation

ROADMAP

Later

Attention analytics dashboard (reads per post, author reputation leaderboard)
MINT:READ supply ceiling integration (ceiling gate on every mint call)

VOCAB

Term	Definition
COIN	Economic shadow of WORK — every mint ledgered, every burn evidenced. INTERNAL governance primitive. Never shown to end users.
CREDITS	External user-facing branding of COIN. All UI surfaces MUST display "Credits" — never "COIN". 1 CREDIT = 1 COIN = $1.00.
MINT	Creation of COIN from validated work
BURN	Destruction of COIN from governance regression

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