{"slug":"canonical/adr/ADR-2026-09-04-01-founder-architecture-flow-adoption","title":"ADR-2026-09-04-01 — Founder Architecture Flow (2026-09-04) adopted as operating-model alignment reference","section":"canonical","sectionLabel":"Canon","status":"canon","type":"adr","path":"canonical/adr/ADR-2026-09-04-01-founder-architecture-flow-adoption.md","bytes":6056,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** APPROVED — 2026-09-04 (founder-delivered conversation record); recorded 2026-09-04\n\n## Ruling\n\nThe founder's consolidated **Spine Architecture Flow** conversation (2026-09-04 01:47, ChatGPT\nrecord, five questions) is adopted **verbatim** into the canonical tree as\n[`FOUNDER-ARCHITECTURE-FLOW-2026-09-04.md`](../FOUNDER-ARCHITECTURE-FLOW-2026-09-04.md), following\nthe `FOUNDER-CANON-2026-08-31.md` precedent. It is the founder-level consolidation of the complete\noperating model and sits **downstream** of the Founder Canon (2026-08-31), the Final Framing /\nFull End-to-End framings (2026-09-03) and the Canon 6.1.0 suite\n([ADR-2026-09-03-05](ADR-2026-09-03-05-founder-canon-6-1-schema-ssot-expansion.md)). It expands and\nconnects them; it does not redefine their constitutional boundaries.\n\n## What the conversation consolidates\n\n1. **Canonical tenant-to-work operating loop** — tenant schema → connected tools → ingestion\n   (Flows A/B/C/D) → triage (classify / link-dedupe / prioritize) → Spine hydration → evidence /\n   knowledge / memory intake → projection (role × department × industry × authority × context) →\n   Human Workbench → context assembly → Twin/AI Workbench → **Work** → capability fabric →\n   governance → Hermes → source systems → re-ingestion → verification → reconciliation → Spine →\n   re-projection → next work.\n2. **Final goal alignment** — product hierarchy, common stable shell (Home / My Work /\n   Communications / Personal / Work / Platform / Administration), adaptive Work area, dual\n   workbenches sharing Business Context + Work but not private memory, Spine Agents coordinating\n   through Work/evidence/handoff, platform and administration shells, marketing hierarchy.\n3. **Projection → table → frontend → backend → storage → memory → retrieval mapping** — no\n   physical table per projection; the **Projection Binding Registry** as the traceability master\n   record; the **six storage layers** (structured SQL · Redis/KV hot state · R2 media ·\n   conversational store · vector search · agent/continuity memory); evidence chains\n   (`source_links` → chunk → retrieval → `intelligence_evidence` → AI output); assembled Twin\n   context (ActiveContextBundle); governed write paths.\n4. **Connector flow, ingestion pipeline, GTM and go-live** — four entry surfaces (Plugin\n   Marketplace, MCP Marketplace, Connector Marketplace, Direct Workbench); connector contract →\n   discovery → category resolution → capability activation → mapping → flow activation; ingestion\n   pipeline; **creamy initial hydration → breadth hydration → full continuous sync**; the three\n   flows kept distinct (Customer Activation / Continuity-Work / GTM Go-Live); the frozen go-live\n   promotion train in **five phases** — Shared Contracts → Customer Zero Plugin → Customer Zero\n   MCP + Workbench → Externalization → Publication.\n5. **End-to-end writeup** — the whole model restated as one narrative with the final technical\n   definition.\n\n## New named structures introduced (to be tracked, not silently renamed)\n\n- **Projection Binding Registry** — no prior repository reference; the traceability chain\n  frontend → projection → view → entity → field → canonical table → storage layer → source.\n- **Projection Platform API** — the single authorized read/compose boundary (frontend never reads\n  storage or providers directly).\n- **Six storage layers** — implementation mapping consistent with the four-plane hybrid\n  ([ADR-2026-09-03-04](ADR-2026-09-03-04-cloudflare-do-hybrid-infrastructure.md)); the 6.1 rule\n  stands: physical storage is an implementation detail, the logical contract governs.\n- **Creamy → breadth hydration** — onboarding doctrine: first session already contains useful\n  business context; coverage expands without delaying first value.\n\n## Reconciliation flags (read with these, not against them)\n\n- **F-1 · Coworker phrasing.** The record's headings (\"Twin + Coworker = contextual AI work\n  layer\", \"TWIN / COWORKER\") reuse the word `coworker`. Per register `G-03`, a distinct Coworker\n  component is **retired, absorbed into Twin**; the record's own text uses `coworker` as a common\n  noun (\"the human-facing AI coworker\"). Read it that way unless the founder re-freezes a separate\n  Coworker surface.\n- **F-2 · Marketing hero line.** \"**One Workspace. Shared Work. Human + AI.**\" is a candidate\n  formulation inside the record. The Final Framing frozen elements (category \"The\n  Self-Organizing Workspace\", tagline \"One spine. Every operation. Governed.\") remain frozen until\n  the founder explicitly replaces them.\n- **F-3 · v11.0 Master Lock (2026-01-16) is superseded.** The January \"no-miss\" marketing pack\n  (`Cognitive Twin`, `IQ Hub`, `Governor Slack`, `AI-Relay Gateway`, `Business OS`, `Today`,\n  Load→Store→Think→Act→Govern) predates the Founder Canon authority stack. Term mapping to current\n  vocabulary: Cognitive Twin → **Twin**; IQ Hub → **Personal** surfaces (notes / knowledge /\n  brainstorming) and Spine knowledge promotion; Governor Slack → **Governance** approvals via\n  governed channels; AI-Relay Gateway → governed execution boundary (**Capability Fabric +\n  Governance + Hermes**); Business OS → **Executive projection**; role-based Views → **adaptive\n  Work projections**. Archive references are lineage evidence; active-file drift is recorded as\n  register `G-22`.\n\n## Consequences\n\n- Architecture, UI, connector, GTM and go-live discussions now have one founder-approved narrative\n  reference; the roadmap's Phase 10 (validation, go-live) remains the delivery plan of record\n  until the founder adopts the five-phase go-live train into `ROADMAP.md`.\n- Register entry `G-22` records the stale v11.0-era doctrine still live in active files.\n- Marketing surfaces may use the record's product/GTM narrative, subject to F-2.\n"}