{"slug":"canonical/adr/ADR-2026-09-03-05-founder-canon-6-1-schema-ssot-expansion","title":"ADR-2026-09-03-05 — Founder Canon 6.1.0 Schema/SSOT expansion suite adopted","section":"canonical","sectionLabel":"Canon","status":"canon","type":"adr","path":"canonical/adr/ADR-2026-09-03-05-founder-canon-6-1-schema-ssot-expansion.md","bytes":3659,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** APPROVED — 2026-09-03 (founder delivery); recorded 2026-09-04\n\n## Ruling\n\nThe founder delivered the **Canon 6.1.0 — Schema/SSOT expansion** suite on 2026-09-03 as a\ndownstream documentation update to the Founder Canon (31 August 2026). It is adopted **verbatim**\ninto this tree:\n\n| Document | Class | Role |\n|---|---|---|\n| [`00-SPINEWORKSPACE-INTEGRATEWISE-CANON-6.1.md`](../00-SPINEWORKSPACE-INTEGRATEWISE-CANON-6.1.md) | Canonical downstream expansion (v6.1.0) | Logical Business Context Spine contract: universal record envelope (§3), canonical entity model (§4), KPI contract (§6), human/AI interaction metadata (§7), Work (§8), Signal (§9), connector → Spine mapping (§11), source precedence (§13), four flows (§14), canonical write rule (§15), capability (§16), governance (§17), execution/closure (§18), ContinuityRun (§19), completeness invariant (§21) |\n| [`02-BUSINESS-CONTEXT-SPINE-6.1.md`](../02-BUSINESS-CONTEXT-SPINE-6.1.md) | Canonical downstream schema specification | Fills the Appendix B `02-` slot: SSOT rule, canonical object inventory, domain coverage, connector-to-object mapping, KPI → Signal → Work chain, completeness test |\n| [`06-CONNECTOR-SCHEMA-CAPABILITY-CONTINUITY-6.1.md`](../06-CONNECTOR-SCHEMA-CAPABILITY-CONTINUITY-6.1.md) | Canonical downstream implementation specification | Universal connector mapping spec: 12-stage semantic install, mapping precedence, conflict states, capability/KPI/signal activation, revocation lifecycle, connector independence |\n\nThe suite is a **later founder decision** and sits at precedence level 1 of the README source\norder — but only within the scope it claims for itself. By its own authority statement it\n**expands the logical Business Context Spine contract without changing** the Founder Canon's\nproduct hierarchy, memory boundaries, authority model, execution model or four-flow architecture.\nWhere the suite and the Founder Canon disagree on those boundaries, the Founder Canon and\n[`00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md`](../00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md) govern.\n\n## What this changes\n\n- The constitutional statement in `00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` is **not** rewritten;\n  it remains the in-tree statement of the Founder Canon. The 6.1 suite extends it below the\n  constitutional layer.\n- `02-BUSINESS-CONTEXT-SPINE-6.1.md` occupies the Appendix B `02-` slot as a versioned delivery.\n  The generic (unversioned) `02-BUSINESS-CONTEXT-SPINE.md` remains unwritten until a non-versioned\n  restatement is needed.\n- `06-CONNECTOR-SCHEMA-CAPABILITY-CONTINUITY-6.1.md` is **not** the Appendix B\n  `06-IDENTITY-CONFIG-INTEGRATION-DISCOVERY-ACTIVATION.md` slot; that slot stays deliberately\n  absent.\n- [`17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md`](../17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md)\n  is refreshed against this suite (survey of 2026-09-03 at commit `22013618`), adding gaps\n  `G-17`–`G-21`: entity ontology/universal envelope (G-17), versioned field-mapping plane and\n  conflict resolution (G-18), first-class KPI and Signal objects (G-19), formal Work identity and\n  ContinuityRun (G-20), connector revocation lifecycle (G-21).\n\n## Consequences\n\n- Schema, mapping, KPI/signal, Work/continuity and connector-lifecycle work now measures against\n  the 6.1 contracts, not ad-hoc interpretations of them.\n- Connector-specific documents may extend mappings but may not redefine canonical business\n  entities (suite §22).\n- Physical storage remains an implementation detail; the logical contract is what the suite fixes.\n"}