{"slug":"canonical/README","title":"Canonical Documentation Root","section":"canonical","sectionLabel":"Canon","status":"canon","type":"document","path":"canonical/README.md","bytes":7590,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nThis directory is the single authoritative documentation tree for IntegrateWise and\nSpineWorkspace. It exists to enforce one rule:\n\n> **CANON is where SpineWorkspace is going. ALIGNMENT is where the repository actually stands.\n> A document describing the second may never redefine the first.**\n\n## Why this directory exists\n\nBefore this tree, four documents in three roots each claimed canonical authority, and they\ndisagreed with each other and with the current Founder Canon. A newer founder decision could\ntherefore be silently overridden by an older repository artifact simply because the artifact was\nchecked in and said \"frozen source of truth\" at the top. See\n[`17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md`](17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md) entry `G-08`.\n\n## The two document classes\n\n| Class | Purpose | May define architecture? | Documents |\n|---|---|---|---|\n| **Canon** | States the decided target architecture. | **Yes** — `00` only. | `00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` |\n| **Alignment** | Reports the observed state of the repository at a commit. | **Never.** | `17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md` |\n\nAn alignment document is a measurement. When it disagrees with canon, that disagreement is a\n**gap to close in code**, not an amendment to canon. Alignment documents are always stamped with\nthe commit they describe, because they go stale the moment the tree moves.\n\n## Source precedence\n\nWhen two sources conflict, the higher entry wins:\n\n1. **Founder decisions** — the current Founder Canon, and any later founder decision.\n2. **`00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md`** and the ADRs under [`adr/`](adr/) — the recorded form of (1).\n3. **The Aug 1 canonical freeze** — implementation baseline and architecture evidence, retained\n   only where it does not conflict with (1) or (2).\n4. **Earlier architecture documents and code** — supporting evidence.\n5. **External market research** — validation and category framing only. Never redefines\n   architecture.\n\n## Rules\n\n- `00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` is the **only** document permitted to redefine\n  architecture. Everything else explains, measures, or implements one part of it.\n- Every file must declare whether it is **canonical**, a **downstream implementation\n  specification**, an **evidence/readiness report**, or **archived history**.\n- Changing canon requires an ADR under [`adr/`](adr/). Editing `00` without one is a defect.\n- Superseded documents are stamped with a supersession banner pointing here. They are not\n  deleted — lineage is evidence.\n- Alignment documents carry a commit SHA and a date in their header. An alignment document\n  without one is void.\n\n## Target structure\n\nThe Founder Canon (Appendix B) prescribes this set. Slots not yet written are **deliberately\nabsent rather than stubbed** — an empty canonical document is worse than a missing one, because it\nreads as decided.\n\n```text\ndocs/canonical/\n  00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md          ✅ written\n  01-SPINEWORKSPACE-OPERATING-MODEL.md              ✅ written (v0.1.0, proposed — fills the 01 slot; integrated operating model)\n  02-BUSINESS-CONTEXT-SPINE.md                      ✅ written (as 02-BUSINESS-CONTEXT-SPINE-6.1.md)\n  03-HUMAN-WORKBENCH-AND-PERSONAL-MEMORY.md\n  04-AI-WORKBENCH-TWIN-AGENTS-AND-AI-MEMORY.md\n  05-WORK-CONTINUITY-AND-HANDOFF.md\n  06-IDENTITY-CONFIG-INTEGRATION-DISCOVERY-ACTIVATION.md\n  07-INGESTION-FOUR-FLOWS-AND-GOVERNED-WRITES.md\n  08-PROJECTION-UI-AND-CONTEXT-COMPOSITION.md\n  09-CAPABILITY-FABRIC-AND-ADK.md\n  10-GOVERNANCE-AUTHORITY-AND-APPROVAL.md\n  11-HERMES-EXECUTION-AND-PROVIDERS.md\n  12-SYNC-VERIFICATION-RECONCILIATION.md\n  13-MEMORY-KNOWLEDGE-EVIDENCE-AND-PRIVACY.md\n  14-MCP-CONTINUITY-BRIDGE-MARKETPLACE-SDK.md\n  15-SECURITY-TENANCY-AUDIT-OBSERVABILITY.md\n  16-ONBOARDING-CUSTOMER-ZERO-AND-GO-LIVE.md\n  17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md   ✅ written\n  18-CANONICAL-GLOSSARY.md                          ✅ written (v0.1.0, proposed — ubiquitous language)\n  contracts/\n  adr/                                              ✅ 23 records\n  archive/\n```\n\n### The operating model and the agent contract (2026-09-04)\n\n[`01-SPINEWORKSPACE-OPERATING-MODEL.md`](01-SPINEWORKSPACE-OPERATING-MODEL.md) is the integrated,\nsource-grounded statement of the full operating model (OneAuth host-controlled entry, eight-form\ndiscovery, host-first capability routing, connector projections, three marketplace catalogs,\nactivation stages, Spine Fabric, dual Workbenches, Work coordination, governance/Hermes closure,\nBridge, memory promotion, GTM/go-live, twenty canonical laws). It is the **target operating\nmodel** — status `proposed` until founder-verified — and it does not redefine `00`; the delta\nbetween it and the code is measured evidence-only in the `17-` register.\n[`18-CANONICAL-GLOSSARY.md`](18-CANONICAL-GLOSSARY.md) freezes the ubiquitous language.\n\nThe ten founding laws with implementation consequence are recorded as focused ADRs\n`ADR-2026-09-04-04` … `ADR-2026-09-04-13` under [`adr/`](adr/) — one decision each, supersede\nrather than rewrite. Agent behavior in this repository is governed by\n[`docs/agent-context/AGENT-OPERATING-CONTRACT.md`](../agent-context/AGENT-OPERATING-CONTRACT.md)\n(mandatory reading order, survey-before-proposal, evidence-only status labels) and its\n[Repository Archaeology Protocol](../agent-context/REPOSITORY-ARCHAEOLOGY-PROTOCOL.md).\n\n### Landed 6.1 suite (2026-09-03 founder delivery)\n\nThe founder's **Canon 6.1.0 — Schema/SSOT expansion** suite is adopted verbatim and recorded in\n[`adr/ADR-2026-09-03-05-founder-canon-6-1-schema-ssot-expansion.md`](adr/ADR-2026-09-03-05-founder-canon-6-1-schema-ssot-expansion.md):\n\n- `00-SPINEWORKSPACE-INTEGRATEWISE-CANON-6.1.md` — canonical downstream expansion (v6.1.0): the\n  logical Spine contract (envelope, entities, KPI, Signal, Work, mapping, governance, execution,\n  ContinuityRun, completeness invariant).\n- `02-BUSINESS-CONTEXT-SPINE-6.1.md` — fills the Appendix B `02-` slot as a versioned downstream\n  schema specification (SSOT rule, canonical object inventory, KPI → Signal → Work).\n- `06-CONNECTOR-SCHEMA-CAPABILITY-CONTINUITY-6.1.md` — downstream connector mapping specification.\n  This is **not** the Appendix B `06-IDENTITY-CONFIG-...` slot, which stays unwritten.\n\nThe suite expands the logical Business Context Spine contract only; the Founder Canon and `00`\nstill govern the product hierarchy, memory boundaries, authority model, execution model and\nfour-flow architecture.\n\n### Numbering note\n\nAn earlier draft of this tree used a 00–25 scheme with alignment split across `23-` and `24-`.\nThat numbering came from a **superseded** documentation suite, not the Founder Canon. The set above\nis the canonical one: 00–18, with alignment and the gap register as a **single** document at `17-`.\n\n## Known migration debt\n\nTwo items are recorded here rather than fixed, because both are disruptive moves that deserve\ntheir own change:\n\n- **ADR numbering collides.** Two independent sequences both start at `ADR-001`:\n  `apps/docs/internal/adr/decision-register.md` (001–014) and\n  `apps/web/public/docs/adr/001-007`. New ADRs in this tree use date-namespaced IDs\n  (`ADR-2026-08-31-NN`) so they cannot collide with either. Merging the two legacy sequences into\n  this tree is unfinished work.\n- **Three documentation roots remain.** `docs/` (5 files), `apps/docs/` (1,921),\n  `apps/web/public/docs/` (661). Consolidating them is tracked as `G-08`.\n"}