Canonadr

ADR-2026-09-04-01 — Founder Architecture Flow (2026-09-04) adopted as operating-model alignment reference

Status: APPROVED — 2026-09-04 (founder-delivered conversation record); recorded 2026-09-04

Ruling

The founder's consolidated Spine Architecture Flow conversation (2026-09-04 01:47, ChatGPT
record, five questions) is adopted verbatim into the canonical tree as
FOUNDER-ARCHITECTURE-FLOW-2026-09-04.md, following
the FOUNDER-CANON-2026-08-31.md precedent. It is the founder-level consolidation of the complete
operating model and sits downstream of the Founder Canon (2026-08-31), the Final Framing /
Full End-to-End framings (2026-09-03) and the Canon 6.1.0 suite
(ADR-2026-09-03-05). It expands and
connects them; it does not redefine their constitutional boundaries.

What the conversation consolidates

  1. Canonical tenant-to-work operating loop — tenant schema → connected tools → ingestion
    (Flows A/B/C/D) → triage (classify / link-dedupe / prioritize) → Spine hydration → evidence /
    knowledge / memory intake → projection (role × department × industry × authority × context) →
    Human Workbench → context assembly → Twin/AI Workbench → Work → capability fabric →
    governance → Hermes → source systems → re-ingestion → verification → reconciliation → Spine →
    re-projection → next work.
  2. Final goal alignment — product hierarchy, common stable shell (Home / My Work /
    Communications / Personal / Work / Platform / Administration), adaptive Work area, dual
    workbenches sharing Business Context + Work but not private memory, Spine Agents coordinating
    through Work/evidence/handoff, platform and administration shells, marketing hierarchy.
  3. Projection → table → frontend → backend → storage → memory → retrieval mapping — no
    physical table per projection; the Projection Binding Registry as the traceability master
    record; the six storage layers (structured SQL · Redis/KV hot state · R2 media ·
    conversational store · vector search · agent/continuity memory); evidence chains
    (source_links → chunk → retrieval → intelligence_evidence → AI output); assembled Twin
    context (ActiveContextBundle); governed write paths.
  4. Connector flow, ingestion pipeline, GTM and go-live — four entry surfaces (Plugin
    Marketplace, MCP Marketplace, Connector Marketplace, Direct Workbench); connector contract →
    discovery → category resolution → capability activation → mapping → flow activation; ingestion
    pipeline; creamy initial hydration → breadth hydration → full continuous sync; the three
    flows kept distinct (Customer Activation / Continuity-Work / GTM Go-Live); the frozen go-live
    promotion train in five phases — Shared Contracts → Customer Zero Plugin → Customer Zero
    MCP + Workbench → Externalization → Publication.
  5. End-to-end writeup — the whole model restated as one narrative with the final technical
    definition.

New named structures introduced (to be tracked, not silently renamed)

  • Projection Binding Registry — no prior repository reference; the traceability chain
    frontend → projection → view → entity → field → canonical table → storage layer → source.
  • Projection Platform API — the single authorized read/compose boundary (frontend never reads
    storage or providers directly).
  • Six storage layers — implementation mapping consistent with the four-plane hybrid
    (ADR-2026-09-03-04); the 6.1 rule
    stands: physical storage is an implementation detail, the logical contract governs.
  • Creamy → breadth hydration — onboarding doctrine: first session already contains useful
    business context; coverage expands without delaying first value.

Reconciliation flags (read with these, not against them)

  • F-1 · Coworker phrasing. The record's headings ("Twin + Coworker = contextual AI work
    layer", "TWIN / COWORKER") reuse the word coworker. Per register G-03, a distinct Coworker
    component is retired, absorbed into Twin; the record's own text uses coworker as a common
    noun ("the human-facing AI coworker"). Read it that way unless the founder re-freezes a separate
    Coworker surface.
  • F-2 · Marketing hero line. "One Workspace. Shared Work. Human + AI." is a candidate
    formulation inside the record. The Final Framing frozen elements (category "The
    Self-Organizing Workspace", tagline "One spine. Every operation. Governed.") remain frozen until
    the founder explicitly replaces them.
  • F-3 · v11.0 Master Lock (2026-01-16) is superseded. The January "no-miss" marketing pack
    (Cognitive Twin, IQ Hub, Governor Slack, AI-Relay Gateway, Business OS, Today,
    Load→Store→Think→Act→Govern) predates the Founder Canon authority stack. Term mapping to current
    vocabulary: Cognitive Twin → Twin; IQ Hub → Personal surfaces (notes / knowledge /
    brainstorming) and Spine knowledge promotion; Governor Slack → Governance approvals via
    governed channels; AI-Relay Gateway → governed execution boundary (Capability Fabric +
    Governance + Hermes    ); Business OS → Executive projection; role-based Views → adaptive
    Work projections    . Archive references are lineage evidence; active-file drift is recorded as
    register G-22.

Consequences

  • Architecture, UI, connector, GTM and go-live discussions now have one founder-approved narrative
    reference; the roadmap's Phase 10 (validation, go-live) remains the delivery plan of record
    until the founder adopts the five-phase go-live train into ROADMAP.md.
  • Register entry G-22 records the stale v11.0-era doctrine still live in active files.
  • Marketing surfaces may use the record's product/GTM narrative, subject to F-2.