SERVICES

Purpose

SERVICES is CANONIC.

Defines the structural contract for SERVICES. Scope is the directory name.

For this directory: scope = SERVICES

This contract defines:

1. structure,
2. interface,
3. ecosystem connectivity.

CANON then governs this scope here-and-now under that contract.

SPEC + TRIAD

Canonical LANGUAGE contract:

SPEC = {SCOPE} TRIAD = CANON.md + VOCAB.md + README.md SPEC + TRIAD = BUSINESS

SPEC is the fixed point (scope identity). {SCOPE}.md is governed content at the scope, not SPEC identity.

Structure

Root service domains: AUTH/, BLOG/, BOOK/, CALENDAR/, DEAL/, DECK/, EMAIL/, FINANCIALS/, FORECASTS/, HEALTH/, IMESSAGE/, INTEL/, KYC/, LEARNING/, LEDGER/, LINKEDIN/, MAGIC/, PAPER/, PATENT/, PLAYBOOKS/, RESERVES/, SHOP/, TALK/, VAULT/, VITAE/.

Services define schemas and contracts. Instances live at USER level (see Instance Pattern below).

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/.

Tier Template

This scope inherits MAGIC tier algebra; service shapes are cumulative:

COMMUNITY = TRIAD BUSINESS = SPEC + TRIAD ENTERPRISE = BUSINESS + COVERAGE.md + ROADMAP.md AGENT = ENTERPRISE + LEARNING.md MAGIC = FULL (255)

Economic Architecture

Primitives: CHAT, INTEL, COIN. Services compose primitives. Projections connect services. Economic events and rules are governed by VOCAB and the services that own them.

Lifecycle

DISCOVER -> GOVERN -> RUN -> LEDGER -> CLOSE -> LEARN

1. DISCOVER: find governed scopes by path.
2. GOVERN: apply CANON constraints and route contracts.
3. RUN: compile runtime surfaces from governance.
4. LEDGER: append WORK and economic events.
5. CLOSE: reconcile monthly economics and publish summary state.
6. LEARN: backprop patterns into LEARNING artifacts.

Routes

Every governed service scope MUST declare a https:// frontend and a magic:// native route in its {SCOPE}.md contract.

Minimum required declaration:

1. web_docs (canonical SPA root): https://{org-user}.github.io/
2. web_surface (this scope within the SPA): https://{org-user}.github.io/{PATH}/
3. magic (canonical native URL): magic://{org-user}.github.io/{PATH}/ (same namespace as web, different transport)

Optional (recommended when applicable):

1. web_app (interactive UI): https://{org-user}.github.io/{APP_PATH}/

All routes MUST be deterministic and stable across deploys.

For this scope (SERVICES):

web_docs: https://hadleylab-canonic.github.io/
web_surface: https://hadleylab-canonic.github.io/SERVICES/
magic:    magic://hadleylab-canonic.github.io/SERVICES/

Fleet Mapping

Single governed mapping source: ~/.canonic/services-manifest.json.

Fleet mapping rules:

1. Service discovery source is DEXTER/SERVICES/**/CANON.md (path-discovered).
2. Instance discovery source is DEXTER/{PLURAL}/**/CANON.md (path-discovered).
3. Fleet/catalog scope mapping MUST be generated from the manifest scopes[].scope.
4. Frontend/runtime surfaces MUST consume the generated mapping; no second hand-curated mapping table.
5. Catalog sync gate MUST fail if a governed scope required for frontend accessibility is missing from fleet mapping output.
6. Runtime projection MUST remain a thin wrapper over magic.c validation (min code, max governance).

Instance Pattern

Services that produce artifacts MUST declare an Instance Pattern in their {SCOPE}.md.

SERVICE (schema):    SERVICES/{SINGULAR}/     ← contract, routes, spec
INSTANCE (content):  {USER}/{PLURAL}/         ← artifacts, projections, instance governance

Instance directories carry their own governance triad + projection file:

{USER}/{PLURAL}/
  {PLURAL}.md      ← instance spec
  CANON.md         ← instance governance
  SHOP.md          ← public projection (or VAULT.md for private)
  COVERAGE.md      ← compliance
  LEARNING.md      ← learning trail
  README.md        ← scope readme
  ROADMAP.md       ← scope roadmap
  VOCAB.md         ← scope vocabulary

Reference implementation: SERVICES/VITAE/VITAE.md → DEXTER/VITAE/.

Projections

Projections follow instances, not services. Projection files live at instance level:

• {USER}/{PLURAL}/SHOP.md — public projection
• {USER}/{PLURAL}/VAULT.md — private projection (auth-gated)

Discovery: walk {USER}/**/SHOP.md and {USER}/**/VAULT.md. Aggregation: compiler builds unified surfaces from discovered projections. Instance: a service projected through user governance context. Computed, not duplicated.

Ecosystem Connectivity

1. Upstream: DEXTER governance roots and DEXTER/PATENTS/ learning evidence.
2. Runtime: ~/.canonic services/generator outputs and attestations.
3. Frontend: governed catalog sync; all governed scopes must be surfaced.
4. Ledger plane: services consume ledgered artifacts through declared consumer gates.

Pages

Default: Overview.

Service Catalog

28 governed services. Every one audit-ready.