DEAL

Axiom

DEAL governs relationships. Every deal ledgered. Every stage evidenced.

Constraints

MUST:     Ledger all deal events
MUST:     Link to governed contacts
MUST:     Evidence every stage transition
MUST:     Every child instance at DEALS/ inherits these constraints
MUST:     Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB)
MUST NOT: Store secrets in public surfaces
MUST NOT: Hardcode deal names in law
MUST NOT: Nest instance directories under SERVICES/DEAL/ (service contract is the class, not the instance)

Capabilities

CONTACT_LINK, DEAL_LEDGER, EVIDENCE_CHAIN, STAGE_GATE

COVERAGE: 255/255

SPEC

Purpose

DEAL is the relationship. DECK is the artifact. DEAL ends in a contract.

A DEAL is a governed business relationship — the full lifecycle from first contact through signed contract. Every deal scope tracks a specific person or organization: meetings, follow-ups, proposals, negotiations, and economic events. DEAL content is VAULT-gated because it contains sensitive commercial terms, counter-proposals, and private correspondence.

DEAL ≠ DECK. A DECK is a presentation you bring to a deal. A DEAL is the ongoing engagement with a person or institution. The HOWARD deal tracks the relationship with Howard University. The HOWARD deck is the slide deck presented at Howard. One deal may involve many decks. The deal outlives every deck.

Structure

Leaf SERVICE scope. No governed child scopes. Deal content lives in {USER}/DEALS/ (instance scope, VAULT.md projection). Instance follows the Instance Pattern at {USER}/DEALS/.

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

Deal Lifecycle

PROSPECT -> QUALIFY -> PROPOSE -> NEGOTIATE -> CLOSE -> LEDGER

Each stage transition is a governed gate:
  PROSPECT:   First contact logged, INTEL populated
  QUALIFY:    Fit assessment complete, stakeholders identified
  PROPOSE:    DECK delivered, terms outlined
  NEGOTIATE:  Terms iterated, counter-proposals governed
  CLOSE:      Agreement executed, COIN minted
  LEDGER:     Full deal ledgered with evidence chain

Ecosystem Connectivity

Upstream: SERVICES governance contracts and hadleylab-canonic scope inheritance.
Runtime: VAULT-gated deal content. SHOP-safe summaries only in public projection.
Frontend: DEAL scope surfaced through governed catalog at DEALS/ route.
Ledger plane: deal events ledgered (stage transitions, evidence, COIN minted).

Pages

Page	Sections
Overview	Purpose, Structure
Lifecycle	Routes, Deal Lifecycle
Ecosystem	Ecosystem Connectivity

Default: Overview.

Instance Pattern

{USER}/DEALS/
  DEALS.md       <- instance spec
  CANON.md       <- scope governance
  VAULT.md       <- private projection (auth-gated)
  COVERAGE.md    <- compliance
  LEARNING.md    <- learning trail
  README.md      <- scope readme
  ROADMAP.md     <- scope roadmap
  VOCAB.md       <- scope vocabulary

LEARNING

Patterns

| Date | Signal | Pattern | Source | |——|——–|———|——–|

LEARNING | DEAL | _generated

ROADMAP

Now

MARK-MALEK DECK deployed (IP patent counsel)
ATOM-AVINASH DECK deployed (credentialing partnership)

Additional deal DECKs as pipeline grows
Automated CANON.json compilation from INTEL

Later

Self-service DECK generation via MAGIC API
Deal pipeline analytics

VOCAB

Term	Definition
DEAL	Deal room service — governed business relationships (VAULT-gated).

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