Unclassified

00 — Master Canon and Source Registry

Status: Canonical control page

Owner: Architecture and release authority

Review cadence: At every architecture decision and release freeze

Governing order

  1. docs/architecture/ARCHITECTURE_LOCK.md
  2. docs/architecture/IMPLEMENTATION_CONTRACT_v1.1.md
  3. docs/architecture/CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md
  4. docs/architecture/SOURCE_PACK_RECONCILIATION_2026-07-28.md
  5. docs/architecture/FOUR_BUTTONS.md and
    docs/architecture/TWIN_BEHAVIOR.md
  6. docs/architecture/TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.md
  7. docs/architecture/IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md
  8. docs/architecture/PLATFORM_LOCK_v1.0.md
  9. Approved ADRs under docs/superpowers/specs/
  10. Runtime and test evidence in the repository
  11. Verified deployment and Customer Zero evidence
  12. Historical source documents and exports

The frozen docs win when an older Coda page, slide, chat export, branch note, or
implementation comment conflicts with them.

Canonical platform vocabulary

The twelve irreducible terms are:

WORK · CONTEXT · SPINE · CONTINUITY · WORKBENCH · TWIN · CAPABILITY · GOVERNANCE · HERMES · SYNC · BRIDGE · OUTCOME

New product or platform concepts must not be introduced during implementation.
New work assembles existing contracts.

Canonical runtime

Configuration → Integration → Pipeline → Adaptive Spine
→ Workbench Composition → Continuity Bridge → User Workbench
→ Twin → Capability → Governance → Hermes → Sync → Promotion

The pipeline grammar is:

LOAD → NORMALIZE → STORE → THINK → APPROVE → ACT → REPEAT

Source registry rules

Each registered source records:

  • source ID and title;
  • document type and location;
  • owner;
  • creation and last-review date;
  • canonical state;
  • governing page;
  • supersedes / superseded-by links;
  • implementation references;
  • verification evidence;
  • confidentiality and retention class.

Conflict protocol

Do not silently merge incompatible snapshots. Record the conflict, identify the
governing source, mark the losing claim Historical or Superseded, and open an ADR
only if the frozen decision is intentionally being reconsidered.

Current approved decision set

  • Platform Lock v1.0 remains frozen.
  • The Workbench is one user-facing surface.
  • Product comprises Onboarding, the User Workbench, and the Silent Twin.
  • Clerk is browser identity; Gateway resolves membership and tenancy.
  • Neon owns canonical truth; D1/KV are bounded operational state.
  • Flow D binds authority for every Flow A/B/C event.
  • Triage classifies and routes; only Governed Spine Writers commit truth.
  • Aging never creates canonical promotion authority.
  • IW-Spine-Network is published as a Plugin with embedded host UI and as an MCP
    package with the browser Workbench; neither inherits host-app credentials.
  • Pipeline promotion is the sole canonical Spine writer.
  • The public MCP exposes exactly nineteen semantic tools.
  • Governance is a hard gate; Hermes coordinates approved execution.
  • Every installed connector must have account, user, tenant, provider-workspace,
    canonical Spine Connection, and compatible schema evidence.
  • Customer Zero has isolated data, credentials and runtime state; its memory
    never enters Customer Production.

Coda publishing rule

Coda is the maintained knowledge surface, not an independent architecture
authority. Every canonical Coda page links to its repository source and carries
the state vocabulary defined in the wiki home page.