Canon

Canonical Documentation Root

This directory is the single authoritative documentation tree for IntegrateWise and
SpineWorkspace. It exists to enforce one rule:

CANON is where SpineWorkspace is going. ALIGNMENT is where the repository actually stands.
A document describing the second may never redefine the first.

Why this directory exists

Before this tree, four documents in three roots each claimed canonical authority, and they
disagreed with each other and with the current Founder Canon. A newer founder decision could
therefore be silently overridden by an older repository artifact simply because the artifact was
checked in and said "frozen source of truth" at the top. See
17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md entry G-08.

The two document classes

Class	Purpose	May define architecture?	Documents
Canon	States the decided target architecture.	Yes — `00` only.	`00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md`
Alignment	Reports the observed state of the repository at a commit.	Never.	`17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md`

An alignment document is a measurement. When it disagrees with canon, that disagreement is a
gap to close in code, not an amendment to canon. Alignment documents are always stamped with
the commit they describe, because they go stale the moment the tree moves.

Source precedence

When two sources conflict, the higher entry wins:

Founder decisions — the current Founder Canon, and any later founder decision.
00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md and the ADRs under adr/ — the recorded form of (1).
The Aug 1 canonical freeze — implementation baseline and architecture evidence, retained
only where it does not conflict with (1) or (2).
Earlier architecture documents and code — supporting evidence.
External market research — validation and category framing only. Never redefines
architecture.

Rules

00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md is the only document permitted to redefine
architecture. Everything else explains, measures, or implements one part of it.
Every file must declare whether it is canonical, a downstream implementation
specification, an evidence/readiness report, or archived history.
Changing canon requires an ADR under adr/. Editing 00 without one is a defect.
Superseded documents are stamped with a supersession banner pointing here. They are not
deleted — lineage is evidence.
Alignment documents carry a commit SHA and a date in their header. An alignment document
without one is void.

Target structure

The Founder Canon (Appendix B) prescribes this set. Slots not yet written are deliberately
absent rather than stubbed — an empty canonical document is worse than a missing one, because it
reads as decided.

docs/canonical/
  00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md          ✅ written
  01-SPINEWORKSPACE-OPERATING-MODEL.md              ✅ written (v0.1.0, proposed — fills the 01 slot; integrated operating model)
  02-BUSINESS-CONTEXT-SPINE.md                      ✅ written (as 02-BUSINESS-CONTEXT-SPINE-6.1.md)
  03-HUMAN-WORKBENCH-AND-PERSONAL-MEMORY.md
  04-AI-WORKBENCH-TWIN-AGENTS-AND-AI-MEMORY.md
  05-WORK-CONTINUITY-AND-HANDOFF.md
  06-IDENTITY-CONFIG-INTEGRATION-DISCOVERY-ACTIVATION.md
  07-INGESTION-FOUR-FLOWS-AND-GOVERNED-WRITES.md
  08-PROJECTION-UI-AND-CONTEXT-COMPOSITION.md
  09-CAPABILITY-FABRIC-AND-ADK.md
  10-GOVERNANCE-AUTHORITY-AND-APPROVAL.md
  11-HERMES-EXECUTION-AND-PROVIDERS.md
  12-SYNC-VERIFICATION-RECONCILIATION.md
  13-MEMORY-KNOWLEDGE-EVIDENCE-AND-PRIVACY.md
  14-MCP-CONTINUITY-BRIDGE-MARKETPLACE-SDK.md
  15-SECURITY-TENANCY-AUDIT-OBSERVABILITY.md
  16-ONBOARDING-CUSTOMER-ZERO-AND-GO-LIVE.md
  17-IMPLEMENTATION-ALIGNMENT-AND-GAP-REGISTER.md   ✅ written
  18-CANONICAL-GLOSSARY.md                          ✅ written (v0.1.0, proposed — ubiquitous language)
  contracts/
  adr/                                              ✅ 23 records
  archive/

The operating model and the agent contract (2026-09-04)

01-SPINEWORKSPACE-OPERATING-MODEL.md is the integrated,
source-grounded statement of the full operating model (OneAuth host-controlled entry, eight-form
discovery, host-first capability routing, connector projections, three marketplace catalogs,
activation stages, Spine Fabric, dual Workbenches, Work coordination, governance/Hermes closure,
Bridge, memory promotion, GTM/go-live, twenty canonical laws). It is the target operating
model — status proposed until founder-verified — and it does not redefine 00; the delta
between it and the code is measured evidence-only in the 17- register.
18-CANONICAL-GLOSSARY.md freezes the ubiquitous language.

The ten founding laws with implementation consequence are recorded as focused ADRs
ADR-2026-09-04-04 … ADR-2026-09-04-13 under adr/ — one decision each, supersede
rather than rewrite. Agent behavior in this repository is governed by
docs/agent-context/AGENT-OPERATING-CONTRACT.md
(mandatory reading order, survey-before-proposal, evidence-only status labels) and its
Repository Archaeology Protocol.

Landed 6.1 suite (2026-09-03 founder delivery)

The founder's Canon 6.1.0 — Schema/SSOT expansion suite is adopted verbatim and recorded in
adr/ADR-2026-09-03-05-founder-canon-6-1-schema-ssot-expansion.md:

00-SPINEWORKSPACE-INTEGRATEWISE-CANON-6.1.md — canonical downstream expansion (v6.1.0): the
logical Spine contract (envelope, entities, KPI, Signal, Work, mapping, governance, execution,
ContinuityRun, completeness invariant).
02-BUSINESS-CONTEXT-SPINE-6.1.md — fills the Appendix B 02- slot as a versioned downstream
schema specification (SSOT rule, canonical object inventory, KPI → Signal → Work).
06-CONNECTOR-SCHEMA-CAPABILITY-CONTINUITY-6.1.md — downstream connector mapping specification.
This is not the Appendix B 06-IDENTITY-CONFIG-... slot, which stays unwritten.

The suite expands the logical Business Context Spine contract only; the Founder Canon and 00
still govern the product hierarchy, memory boundaries, authority model, execution model and
four-flow architecture.

Numbering note

An earlier draft of this tree used a 00–25 scheme with alignment split across 23- and 24-.
That numbering came from a superseded documentation suite, not the Founder Canon. The set above
is the canonical one: 00–18, with alignment and the gap register as a single document at 17-.

Known migration debt

Two items are recorded here rather than fixed, because both are disruptive moves that deserve
their own change:

ADR numbering collides. Two independent sequences both start at ADR-001:
apps/docs/internal/adr/decision-register.md (001–014) and
apps/web/public/docs/adr/001-007. New ADRs in this tree use date-namespaced IDs
(ADR-2026-08-31-NN) so they cannot collide with either. Merging the two legacy sequences into
this tree is unfinished work.
Three documentation roots remain. docs/ (5 files), apps/docs/ (1,921),
apps/web/public/docs/ (661). Consolidating them is tracked as G-08.