{"slug":"documentation/00-master-canon-and-source-registry","title":"00 — Master Canon and Source Registry","section":"documentation","sectionLabel":"Documentation","status":"unclassified","type":"document","path":"documentation/00-master-canon-and-source-registry.mdx","bytes":3614,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Canonical control page\n\n**Owner:** Architecture and release authority\n\n**Review cadence:** At every architecture decision and release freeze\n\n## Governing order\n\n1. `docs/architecture/ARCHITECTURE_LOCK.md`\n2. `docs/architecture/IMPLEMENTATION_CONTRACT_v1.1.md`\n3. `docs/architecture/CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md`\n4. `docs/architecture/SOURCE_PACK_RECONCILIATION_2026-07-28.md`\n5. `docs/architecture/FOUR_BUTTONS.md` and\n   `docs/architecture/TWIN_BEHAVIOR.md`\n6. `docs/architecture/TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.md`\n7. `docs/architecture/IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md`\n8. `docs/architecture/PLATFORM_LOCK_v1.0.md`\n9. Approved ADRs under `docs/superpowers/specs/`\n10. Runtime and test evidence in the repository\n11. Verified deployment and Customer Zero evidence\n12. Historical source documents and exports\n\nThe frozen docs win when an older Coda page, slide, chat export, branch note, or\nimplementation comment conflicts with them.\n\n## Canonical platform vocabulary\n\nThe twelve irreducible terms are:\n\n`WORK · CONTEXT · SPINE · CONTINUITY · WORKBENCH · TWIN · CAPABILITY · GOVERNANCE · HERMES · SYNC · BRIDGE · OUTCOME`\n\nNew product or platform concepts must not be introduced during implementation.\nNew work assembles existing contracts.\n\n## Canonical runtime\n\n```text\nConfiguration → Integration → Pipeline → Adaptive Spine\n→ Workbench Composition → Continuity Bridge → User Workbench\n→ Twin → Capability → Governance → Hermes → Sync → Promotion\n```\n\nThe pipeline grammar is:\n\n```text\nLOAD → NORMALIZE → STORE → THINK → APPROVE → ACT → REPEAT\n```\n\n## Source registry rules\n\nEach registered source records:\n\n- source ID and title;\n- document type and location;\n- owner;\n- creation and last-review date;\n- canonical state;\n- governing page;\n- supersedes / superseded-by links;\n- implementation references;\n- verification evidence;\n- confidentiality and retention class.\n\n## Conflict protocol\n\nDo not silently merge incompatible snapshots. Record the conflict, identify the\ngoverning source, mark the losing claim Historical or Superseded, and open an ADR\nonly if the frozen decision is intentionally being reconsidered.\n\n## Current approved decision set\n\n- Platform Lock v1.0 remains frozen.\n- The Workbench is one user-facing surface.\n- Product comprises Onboarding, the User Workbench, and the Silent Twin.\n- Clerk is browser identity; Gateway resolves membership and tenancy.\n- Neon owns canonical truth; D1/KV are bounded operational state.\n- Flow D binds authority for every Flow A/B/C event.\n- Triage classifies and routes; only Governed Spine Writers commit truth.\n- Aging never creates canonical promotion authority.\n- IW-Spine-Network is published as a Plugin with embedded host UI and as an MCP\n  package with the browser Workbench; neither inherits host-app credentials.\n- Pipeline promotion is the sole canonical Spine writer.\n- The public MCP exposes exactly nineteen semantic tools.\n- Governance is a hard gate; Hermes coordinates approved execution.\n- Every installed connector must have account, user, tenant, provider-workspace,\n  canonical Spine Connection, and compatible schema evidence.\n- Customer Zero has isolated data, credentials and runtime state; its memory\n  never enters Customer Production.\n\n## Coda publishing rule\n\nCoda is the maintained knowledge surface, not an independent architecture\nauthority. Every canonical Coda page links to its repository source and carries\nthe state vocabulary defined in the wiki home page.\n"}