{"slug":"canonical/adr/ADR-2026-09-04-03-founder-final-architecture","title":"ADR-2026-09-04-03 — Final Architecture writeup adopted; Coworker restored as a distinct concept","section":"canonical","sectionLabel":"Canon","status":"canon","type":"adr","path":"canonical/adr/ADR-2026-09-04-03-founder-final-architecture.md","bytes":4708,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** APPROVED — 2026-09-04 (founder-delivered record); recorded 2026-09-04\n\n## Ruling\n\nThe founder's **\"SpineWorkspace — Final End-to-End Goal & Architecture Writeup\"** (2026-09-04\n02:45, the newest of the three 2026-09-04 records) is adopted **verbatim** as\n[`FOUNDER-FINAL-ARCHITECTURE-2026-09-04.md`](../FOUNDER-FINAL-ARCHITECTURE-2026-09-04.md). Where\nits wording refines the earlier 2026-09-04 records\n([ADR-2026-09-04-01](ADR-2026-09-04-01-founder-architecture-flow-adoption.md),\n[ADR-2026-09-04-02](ADR-2026-09-04-02-founder-final-goal.md)), this record's wording is the latest\nfounder formulation.\n\n## What this record locks\n\n- **Final product definition (latest wording):**\n\n  > SpineWorkspace is the shared operating environment where humans and AI work toward the same\n  > business goals through different workbenches, using the same governed Business Context Spine\n  > while maintaining separate human and AI continuity.\n\n- **Boundary litany** (§1): the Spine Fabric is not another application; the Human Workbench is\n  not another truth store; the AI Workbench is not another business system; Twin is not the\n  organizational source of truth; MCP is not the Spine; Agents are not the Spine; connectors do\n  not define the canonical business model by themselves.\n\n- **The mapping contract** (§4): every connector carries an explicit mapping contract — entity,\n  field, relationship, identity, semantic transformation, type conversion, status/value and\n  provenance mappings — so that **one canonical business model serves many connector\n  representations**. Consistent with the 6.1 field-mapping plane (register `G-18`).\n\n- **Source truth vs Spine truth** (§6): source systems remain authoritative for their own\n  operational transactions; the Spine is the governed cross-system business context — it connects\n  their meaning rather than replacing them.\n\n- **Role-based projection chain** (§9): Spine → authority → role → policy → **projection\n  registry** → role-specific projection → user workbench.\n\n- **The architectural boundary, in one sentence** (§24): connectors bring external reality in;\n  mapping translates it into the canonical model; triage governs schema evolution; Spine preserves\n  context and continuity; projection determines what each participant sees; Work coordinates human\n  and AI activity; Capability Fabric determines what can be done; Governance determines whether it\n  may be done; execution changes external reality; reconciliation establishes what actually\n  happened.\n\n- **Final system statement and doctrine** (§25), repeating \"The Workbench is one. The Spine is\n  one. The Projection is many.\" and \"Humans govern. AI helps. Spine preserves continuity.\"\n\n## Coworker restored as a distinct concept — supersedes prior guidance\n\n§13 keeps three AI-side concepts distinct:\n\n- **Twin** — the user's primary AI work partner.\n- **Coworker** — *\"the contextual companion that helps assemble active context and\n  communication.\"*\n- **Spine Agents** — specialized agents performing bounded work through approved capabilities.\n\nThis is a **later founder decision** than the Founder Canon (2026-08-31) resolution recorded in\nregister `G-03` (which retired Coworker as a layer absorbed into Twin). It restores Coworker as a\ndistinct concept with the same scope the workspace instructions have always described: a\ncompanion between active Human Workbench interaction and the Twin — **not a second orchestration\nauthority**. Accordingly:\n\n- Register `G-03` carries an update annotation pointing here; its original text stands as the\n  dated measurement of the 2026-08-31 canon era.\n- Flag F-1 in [ADR-2026-09-04-01](ADR-2026-09-04-01-founder-architecture-flow-adoption.md) is\n  superseded: `coworker` need not be read as a common noun only.\n- Product and UI surfaces may use **Coworker** for the contextual companion role.\n\n## Vocabulary note\n\n§11's diagram labels the AI-side workbench \"TWIN WORKBENCH\". That is a label slip inside the\nrecord, not a re-freeze: the canonical term remains **AI Workbench** per\n[ADR-2026-08-31-01](ADR-2026-08-31-01-ai-workbench-supersedes-twin-workbench.md), and the deck QA\ntooling scans for the retired phrase. The record's own §11/§12 prose uses AI Workbench correctly.\n\n## Consequences\n\n- This record is the shortest complete statement of the intended end state; use §24 and §25 as\n  the canonical summary chain for implementation and communication work.\n- Schema/connector work continues to measure against the 6.1 suite and register G-17–G-22; this\n  record adds no new code findings.\n"}