Canonadr

ADR-2026-09-03-05 — Founder Canon 6.1.0 Schema/SSOT expansion suite adopted

Status: APPROVED — 2026-09-03 (founder delivery); recorded 2026-09-04

Ruling

The founder delivered the Canon 6.1.0 — Schema/SSOT expansion suite on 2026-09-03 as a
downstream documentation update to the Founder Canon (31 August 2026). It is adopted verbatim
into this tree:

DocumentClassRole
00-SPINEWORKSPACE-INTEGRATEWISE-CANON-6.1.mdCanonical 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)
02-BUSINESS-CONTEXT-SPINE-6.1.mdCanonical downstream schema specificationFills the Appendix B 02- slot: SSOT rule, canonical object inventory, domain coverage, connector-to-object mapping, KPI → Signal → Work chain, completeness test
06-CONNECTOR-SCHEMA-CAPABILITY-CONTINUITY-6.1.mdCanonical downstream implementation specificationUniversal connector mapping spec: 12-stage semantic install, mapping precedence, conflict states, capability/KPI/signal activation, revocation lifecycle, connector independence

The suite is a later founder decision and sits at precedence level 1 of the README source
order — but only within the scope it claims for itself. By its own authority statement it
expands the logical Business Context Spine contract without changing the Founder Canon's
product hierarchy, memory boundaries, authority model, execution model or four-flow architecture.
Where the suite and the Founder Canon disagree on those boundaries, the Founder Canon and
00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md govern.

What this changes

  • The constitutional statement in 00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md is not rewritten;
    it remains the in-tree statement of the Founder Canon. The 6.1 suite extends it below the
    constitutional layer.
  • 02-BUSINESS-CONTEXT-SPINE-6.1.md occupies the Appendix B 02- slot as a versioned delivery.
    The generic (unversioned) 02-BUSINESS-CONTEXT-SPINE.md remains unwritten until a non-versioned
    restatement is needed.
  • 06-CONNECTOR-SCHEMA-CAPABILITY-CONTINUITY-6.1.md is not the Appendix B
    06-IDENTITY-CONFIG-INTEGRATION-DISCOVERY-ACTIVATION.md slot; that slot stays deliberately
    absent.
  • 17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md
    is refreshed against this suite (survey of 2026-09-03 at commit 22013618), adding gaps
    G-17–G-21: entity ontology/universal envelope (G-17), versioned field-mapping plane and
    conflict resolution (G-18), first-class KPI and Signal objects (G-19), formal Work identity and
    ContinuityRun (G-20), connector revocation lifecycle (G-21).

Consequences

  • Schema, mapping, KPI/signal, Work/continuity and connector-lifecycle work now measures against
    the 6.1 contracts, not ad-hoc interpretations of them.
  • Connector-specific documents may extend mappings but may not redefine canonical business
    entities (suite §22).
  • Physical storage remains an implementation detail; the logical contract is what the suite fixes.