{"slug":"strategy/product-strategy/LAYER_OWNERSHIP_AND_TWIN_RUNTIME","title":"IntegrateWise — Layer Ownership & Twin Runtime Doctrine","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/product-strategy/LAYER_OWNERSHIP_AND_TWIN_RUNTIME.mdx","bytes":11303,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Date:** 2026-06-09 | **Authority:** Nirmal (Founder) | **Version:** 1.0\n> **Status:** LOCKED — canonical layer ownership definition\n> **Supersedes:** Prior L1-L4 descriptions in IW_FRONTEND_ARCHITECTURE.md (Nuxt/Vue doc is deprecated)\n> **Companions:** CANONICAL_TAXONOMY.md, ARCHITECTURE_AND_DATA_FLOW.md, MCP_ADK_ROUTING_SPINE_MEMORY_ARCHITECTURE.md\n\n---\n\n## The Architectural Statement\n\n```\nOpen WebUI powers the Twin.\nIntegrateWise powers the intelligence.\n```\n\nOpen WebUI is not a feature source. It is a **runtime**.\n\nMost teams start with: Product → Chat → AI.\nIntegrateWise ends with:\n\n```\nProduct\n  ├── Work        (L1)\n  ├── Awareness   (L2)\n  ├── Twin Runtime (L3)\n  └── Memory      (L4)\n```\n\nThis is fundamentally different. The moat is not the chat. The moat is the\nawareness layer, the governed memory loop, and the Spine abstraction.\n\n---\n\n## Final Layer Ownership\n\n### L1 — Workspace\n\n```\nPurpose:    DO WORK\nOwner:      IntegrateWise (apps/web)\nNav:        Sections in the left nav (Desk, Inbox, Entity360, domains, tasks, etc.)\nStatus:     ALREADY BUILT — 12 domains × 20-47 views each, wired to Spine\nContains:   Desk · Inbox · Entity360 · Tasks · Pipeline · Projects\n            Reports · Approvals · Actions · Triage · Domain Views (12)\n\nOpen WebUI does not own this. These are nav sections in apps/web.\n```\n\n**Code:** `apps/web/src/components/l1/` (12 domains × views)\n**Shell:** `workspace-shell-new.tsx` (Personal / Work toggle)\n**Data:** `useSpineProjection` → gateway → D1 spine_vault (real Spine data, no mock)\n\n---\n\n### L2 — Awareness\n\n```\nPurpose:    NOTICE\nOwner:      IntegrateWise (apps/web)\nNav:        Sections in the left nav (Signals, Insights, Scoring, Evidence, Triage)\nStatus:     SPLIT OUT — now nav sections, not just a bottom drawer\nContains:   Signals · Scoring · Predictions · Insights · Evidence\n            Lineage · Readiness · Triage · Governance Queue\n\nThis is the real moat. Nav sections in the same app.\nThe overlay drawer ALSO exists for urgent signals that interrupt work.\n```\n\n**Code:** `apps/web/src/components/l2/` (cognitive/, insights/, signals/, spine/)\n**Trigger:** `cognitive-triggers.tsx` — role-based thresholds still fire the drawer\n**Nav sections:** Signals, Insights, Evidence, Triage — accessible from left nav directly\n\n---\n\n### L3 — Twin Runtime\n\n```\nPurpose:    THINK\nOwner:      Open WebUI (DEPLOYED INSTANCE — we don't build it)\nNav:        Section in the left nav (Twin) — links/embeds to OWUI\nStatus:     LIVE at twin.integratewise.ai (Hostinger)\nContains:   Conversation · Voice · Planning · Reasoning · Research\n            Execution · Playbooks · Tool Usage · Briefings\n\nThe Twin is the Conversation Layer for the Spine.\nOWUI is a deployed instance we USE. Not code we maintain.\n```\n\n**Runtime:** Open WebUI instance (deployed, Hostinger)\n**URL:** twin.integratewise.ai\n**Integration:** iframe embed in apps/web OR external link from nav\n**Bridge:** continuity-tool-server → pipeline → Spine\n\n---\n\n### L4 — Library (Memory)\n\n```\nPurpose:    KNOW\nOwner:      IntegrateWise (apps/web)\nNav:        Sections in the left nav (Org Memory, Personal, Decisions, Doctrine, Knowledge)\nStatus:     BUILT — memory views wired to Spine\nContains:   Org Memory · Personal Memory · Book of Projects · Doctrine\n            Decisions · Research · Playbooks · Knowledge Assets\n\nThe permanent memory substrate. Nav sections in the same app.\nThe Twin reads from it. The Twin does not own it.\n```\n\n**Code:** `apps/web/src/components/l1/knowledge/` + memory views\n**Projection:** Also syncs to Coda (L4 external) via `coda-pack/sync-org-memory.ts`\n\n---\n\n## The Left Nav Structure (one app, all layers)\n\n```\nLEFT NAV — apps/web\n─────────────────────────────────────────\n  L1 WORK\n    Desk            /desk\n    Inbox           /inbox\n    Entity 360      /entity360\n    [Domain views]  /work/*\n    Tasks           /work/tasks\n    Projects        /work/projects\n    Reports         /work/grow\n\n  L2 AWARENESS\n    Signals         /signals\n    Insights        /insights\n    Triage          /triage\n    Evidence        /evidence\n\n  L3 TWIN\n    Twin            /twin  (embeds/links OWUI)\n\n  L4 MEMORY\n    Org Memory      /memory/org\n    Personal        /memory/personal\n    Decisions       /memory/decisions\n    Knowledge       /knowledge\n\n  SYSTEM\n    Connectors      /connectors\n    Settings        /settings\n    Profile         (toggle)\n─────────────────────────────────────────\n```\n\nAll four layers are **nav sections in one app**. Not four separate apps.\nNot four separate surfaces. One left nav. One shell. One surface.\nL3 is the only external link (OWUI deployed instance).\n\n#### What Open WebUI Provides (must use)\n\n| Feature         | IW Usage                                            |\n| --------------- | --------------------------------------------------- |\n| Chat (core)     | Conversation with the Twin                          |\n| Voice           | x.ai \"eve\" hands-free                               |\n| File uploads    | Drop docs for Twin to reason over                   |\n| Web search      | Agent Zero searches + cites                         |\n| Code execution  | Open Terminal (run code in sandbox)                 |\n| MCP support     | 4 tool servers connected                            |\n| Model presets   | \"IW Twin\" preset (doctrine + tools + Spine context) |\n| Knowledge (RAG) | Doctrine + org_memory loaded as collections         |\n| Bound tools     | Force-enabled per agent config                      |\n| Agent runtime   | Agent Zero multi-step execution                     |\n\n#### Nice to Have (later, not v1)\n\n| Feature         | Potential Use                                   |\n| --------------- | ----------------------------------------------- |\n| Automations     | Schedule daily 8am brief trigger                |\n| Task management | Playbook step tracking                          |\n| Slash commands  | `/brief`, `/risk`, `/propose`, `/entity <name>` |\n| Skills          | Doctrine as markdown instruction sets           |\n| Channels        | Team + Twin in same thread (future)             |\n\n#### Ignore (IW already owns better versions)\n\n| Feature         | Why Ignore                                            |\n| --------------- | ----------------------------------------------------- |\n| RBAC / Admin    | CF Access + Gateway handles                           |\n| Analytics       | L1 domain views handle                                |\n| Native Memory   | Spine + governed memory loop is stronger              |\n| Native Auth     | CF Access is sole identity                            |\n| Team Governance | L2 awareness + L1 triage views                        |\n| Notes           | Violates Continuity doctrine — use L4 Library instead |\n\n> **Critical:** Open WebUI Notes must NOT be used. They create a fragmented\n> memory store that violates the Continuity doctrine. Everything durable ends\n> up in: Spine → Library → Governed Memory. Not inside OWUI's database.\n\n---\n\n### L4 — Library (Memory)\n\n```\nPurpose:    KNOW\nOwner:      IntegrateWise\nContains:   Org Memory · Personal Memory · Book of Projects · Doctrine\n            Decisions · Research · Playbooks · Knowledge Assets\n\nThis is the permanent memory substrate.\nThe Twin reads from it.\nThe Twin does not own it.\n```\n\n**Projection surfaces:** Coda (primary L4 for founder), any queryable surface\n**Sync:** `packages/coda-pack/sync-org-memory.ts` (--personal for founder mode)\n**MCP tools:** coda.connect_doc, coda.read_page, coda.sync_memory_to_doc\n**Governance:** Triage Bot governs all writes to org_memory. Twin proposes, never writes.\n**Storage:** R2 (raw) + AI Search/Vectorize (semantic retrieval) + D1 (metadata) + Supabase (fortress, promoted)\n\n---\n\n## Briefings — The Missing Category\n\nBriefings deserve their own classification. Not chat. Not memory. Not signals.\n\n```\nMorning Brief\nWeekly Brief\nAccount Brief\nProject Brief\nDecision Brief\nRisk Brief\nDeployment Brief\n```\n\n**Generated from:** Spine + Signals + Memory + Entity360\n**Rendered through:** Twin (L3)\n**Consumed in:** L1 (/desk) + L3 (Twin speaks first)\n\nBriefings are one of the most-used experiences in the platform. They are the\nTwin's primary OUTPUT that appears in L1 (the morning brief card on /desk) and\nis generated via L3 (MorningContextBuilder → Twin Orchestrator).\n\n---\n\n## The Mental Model\n\n```\nL1 = Work\nL2 = Awareness\nL3 = Reasoning\nL4 = Memory\n\nSpine = Truth\nContinuity Bridge = Access Layer\nTwin = Conversation Layer\n```\n\n---\n\n## Layer Boundaries (hard walls)\n\n```\nL1 ↔ L3:   L1 NEVER embeds chat. Twin outputs surface as cards/proposals in L1.\n            L3 NEVER owns views. It reasons. L1 renders the result.\n\nL2 ↔ L3:   L2 surfaces signals + evidence + [Open Twin ↗].\n            L3 does the thinking when the user clicks through.\n            L2 NEVER reasons. L3 NEVER signals.\n\nL3 ↔ L4:   Twin READS from Library (via MCP/Vectorize).\n            Twin PROPOSES to Library (via memory.propose → governance).\n            Twin NEVER writes to Library directly.\n\nL2 ↔ L4:   L2 may reference memory (evidence context).\n            L4 is not surfaced as an overlay. L4 is a separate projection surface.\n\nOWUI ↔ Spine:  Open WebUI NEVER accesses Spine directly.\n               continuity-tool-server is the ONLY bridge.\n               All OWUI memory features are UNUSED (Spine owns memory).\n```\n\n---\n\n## Ownership Summary\n\n| Layer             | Owner                                               | What Dies If Removed                                  |\n| ----------------- | --------------------------------------------------- | ----------------------------------------------------- |\n| L1 Workspace      | IntegrateWise                                       | All operational views, domain projections, daily work |\n| L2 Awareness      | IntegrateWise                                       | Signals, scoring, predictions, governance — THE MOAT  |\n| L3 Twin Runtime   | Open WebUI (runtime) + IW (intelligence via Bridge) | Reasoning, conversation, voice, planning              |\n| L4 Library        | IntegrateWise                                       | Institutional memory, doctrine, decisions, knowledge  |\n| Spine             | IntegrateWise                                       | Operational truth (entities, relationships, signals)  |\n| Continuity Bridge | IntegrateWise                                       | Access layer (MCP + Gateway + ADK + Auth)             |\n\n**If Open WebUI is swapped for another chat runtime:** L1, L2, L4, Spine, and Bridge are unaffected. Only L3's UI changes. The Twin is model-agnostic AND runtime-agnostic.\n\n**If IntegrateWise is removed and only OWUI remains:** Everything that matters disappears. No awareness. No governance. No memory loop. No entity resolution. No Spine. Just a generic chat app.\n\nThat's where the moat lives.\n\n---\n\n_Open WebUI powers the Twin. IntegrateWise powers the intelligence._\n_The chat is not the product. The continuity is._\n"}