Canonadr

ADR-2026-09-04-02 — Final goal and end-to-end writeup adopted (founder record)

Status: APPROVED — 2026-09-04 (founder-delivered record, designated via /goal); recorded 2026-09-04

Ruling

The founder's "SpineWorkspace — Final End-to-End Writeup" (2026-09-04 02:37, distinct from the
earlier Architecture Flow record) is adopted verbatim into the canonical tree as
FOUNDER-FINAL-GOAL-2026-09-04.md. This is the founder's
designated final goal record for the product's end-to-end model. Its authority sits with the
founder framing stack (Founder Canon 2026-08-31 → Final Framing / Full End-to-End 2026-09-03 →
Canon 6.1.0 suite → Architecture Flow record 2026-09-04 → this record), and it downstream of the
constitutional boundaries those documents fix.

What this record locks

  • Final goal statement:

    SpineWorkspace is the shared business workspace where humans and AI work toward the same
    business goals using the same governed organizational context, while each retains its own
    continuity, permissions, responsibilities and working environment.

  • Architectural rule (new frozen-style formulation):

    The Workbench is one. The Spine is one. The Projection is many.

  • Final system contract (§26): connect the organization's software → discover schemas and
    capabilities → map source data into a governed tenant Spine → hydrate as domains arrive →
    preserve provenance, evidence and continuity → compose role/context projections → humans and
    Twins work the same authorized context for the same Work → Twin prepares, reasons, proposes →
    capabilities execute governed actions via MCP/REST/A2A → approved outcomes write back →
    re-ingest, verify, reconcile → preserve as organizational continuity → project the next work.

  • Spine definition by negation (§2): the Spine is not the CRM, ERP, AI model, MCP, agent
    runtime, UI, connector or a second source system — it is the governed representation of the
    organization's operational context.

  • Downstream field models for KPI (§21), Goal (§22) and Work (§23) — complementary
    elaborations of the Canon 6.1.0 §6 KPI contract, §8 Work contract and the Goal object; no
    conflict, they bind the same objects to business goals and Work context.

  • Closing thesis (§26) — identical to the repository's constitutional product rule already in
    AGENTS.md: "One Workspace. All Connected Software. Business Context.
    Shared Work. Human + AI Working Together."

Vocabulary note

§2's reference to the existing tenant model names DigitalTwin among its shared-context objects.
That is a reference to the legacy tenant-schema object name, not a reintroduction of retired
vocabulary; current canonical vocabulary remains Twin (see ADR-2026-08-31-01 and register
G-03). Code referencing the tenant model may keep the object name; product language must not.

Relationship to the Architecture Flow record

This record and
FOUNDER-ARCHITECTURE-FLOW-2026-09-04.md
(ADR-2026-09-04-01) are complementary: the Flow record carries the operating loop, UI/marketing
alignment, projection-storage mapping and GTM/go-live detail; this record carries the goal
statement, the one-Workbench/one-Spine/many-Projections rule, and the closing system contract.
Where both describe the same structure, they agree.

Consequences

  • Implementation, deck and marketing work should test against the final goal statement and the
    §26 contract as the shortest summary of the intended end state.
  • No code-drift findings arise from this record alone; register G-22 already tracks the live
    v11.0-era doctrine drift.