{"slug":"strategy/product-strategy/ARCHITECTURE_REVIEW","title":"IntegrateWise — Architecture Context & Documentation Rules","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/product-strategy/ARCHITECTURE_REVIEW.mdx","bytes":31157,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> Master reference for all agents, contributors, and documentation authors.\n> Last updated: April 2026\n\n---\n\n## Current Surface-Binding Doctrine\n\n- Operational Workbench = the primary work surface; left sidebar nav; Twin sidebar pops out when needed.\n- Twin Workbench = full AI ecosystem surface (skills, knowledge, agents, prompts, conversational library).\n- Governance is embedded at every layer — not a separate workbench.\n- OpenWebUI is not the customer-facing product shell.\n- Twin / OpenWebUI runtime surfaces use the canonical Forest + Paper system language.\n- Midnight Executive is investor-deck / fundraising language only.\n\nUse older L1/L2 / workspace / knowledge-UI language in this file through that boundary if any historical phrasing remains.\n\n---\n\n## Table of Contents\n\n1. [Product Definition & Terminology](#1-product-definition--terminology)\n2. [Architecture Overview](#2-architecture-overview)\n3. [The Three Data Flows](#3-the-three-data-flows)\n4. [L1 — The Workspace (12 Domain Views)](#4-l1--the-workspace-12-domain-views)\n5. [L2 — The Cognitive Layer (14 Components)](#5-l2--the-cognitive-layer-14-components)\n6. [The Schema System](#6-the-schema-system)\n7. [Entity 360 — Convergence Point](#7-entity-360--convergence-point)\n8. [The Cognitive Loop](#8-the-cognitive-loop)\n9. [Connector Ecosystem](#9-connector-ecosystem)\n10. [The Knowledge Memory](#10-the-knowledge-memory)\n11. [Trust & Governance](#11-trust--governance)\n12. [20 Products Across 3 Surfaces](#12-20-products-across-3-surfaces)\n13. [Founding Story](#13-founding-story)\n14. [Go-To-Market (Current Phase)](#14-go-to-market-current-phase)\n15. [Architectural Review (9.2/10)](#15-architectural-review-9210)\n16. [Documentation Rules — Public vs Internal](#16-documentation-rules--public-vs-internal)\n17. [Writing Style](#17-writing-style)\n18. [Sidebar Structure — Public Docs](#18-sidebar-structure--public-docs)\n19. [Known Issues (Code, Not Docs)](#19-known-issues-code-not-docs)\n20. [Key Source Files](#20-key-source-files)\n\n---\n\n## 1. Product Definition & Terminology\n\n### What IntegrateWise IS\n\nIntegrateWise is a **Knowledge Workspace over the Spine, empowered by AI**.\n\nIt is NOT a platform, NOT an OS, NOT a tool.\n\n### Approved Terms\n\n| Term                           | Usage                                       | Context                                  |\n| ------------------------------ | ------------------------------------------- | ---------------------------------------- |\n| Knowledge Workspace            | Primary descriptor                          | Always use this                          |\n| Spine                          | Default name for the intelligent data layer | Product-level term                       |\n| Adaptive Spine                 | Variant of Spine                            | Glossary synonym — same thing            |\n| Intelligent Spine              | Variant of Spine                            | Glossary synonym — same thing            |\n| Unified Intelligence Layer     | Variant of Spine                            | Glossary synonym — same thing            |\n| Adaptive Layer                 | Variant of Spine                            | Glossary synonym — same thing            |\n| Cognitive Intelligence Overlay | L2 overlay experience                       | Correct as-is — \"overlay\" is intentional |\n| Cognitive Layer                | Short form of above                         | Acceptable                               |\n| TruthLayer                     | Trust/governance system                     | Platform capability, not a product       |\n| Entity 360                     | Convergence point for all 3 flows           | Core view, not standalone product        |\n\n### NEVER Say Externally\n\n- \"We are a platform\"\n- \"We are an AI tool\"\n- \"Cognitive OS\"\n- \"IntegrateWise OS\"\n- \"We replace Gainsight\"\n- \"We are like Salesforce but with AI\"\n\n### Hero Anchor\n\n> \"Your tools don't talk to each other. Your AI doesn't know context. You are the bridge. The Human API.\"\n\n### Trust Line\n\n> \"Every AI remembers. Only IntegrateWise remembers the truth.\"\n\n---\n\n## 2. Architecture Overview\n\nIntegrateWise has two product layers:\n\n### L1 — The Workspace\n\n- 12 domain-specific views\n- Schema-filtered per tenant (industry + department)\n- What users see and work in daily\n\n### L2 — The Cognitive Layer (Overlay)\n\n- 14 components accessible via `Cmd+J`\n- Non-intrusive overlay — sits alongside work, extends when needed\n- Also schema-filtered\n\n### Platform Engine (Under the Hood)\n\n- The Spine (intelligent plumbing connecting all data)\n- Entity 360 (convergence point)\n- Schema system (12 domains × 11 industry overlays)\n- 8-stage processing pipeline (INTERNAL ONLY — never expose publicly)\n- Connector ecosystem\n- Knowledge Memory\n\n```\n┌──────────────────────────────────────────────────┐\n│                   L2 — COGNITIVE OVERLAY          │\n│  (SpineUI, ContextUI, KnowledgeUI, Twin, HITL,   │\n│   Signals, Think, Act, Govern, Adjust, Repeat,    │\n│   Audit Trail, Agent Config, Evidence Drawer)      │\n├──────────────────────────────────────────────────┤\n│                   L1 — WORKSPACE                  │\n│  (12 domain views, schema-filtered per tenant)    │\n├──────────────────────────────────────────────────┤\n│              PLATFORM ENGINE                      │\n│  Spine │ Entity 360 │ Schema │ Pipeline │ Memory  │\n├──────────────────────────────────────────────────┤\n│              CONNECTORS                           │\n│  50+ SaaS │ MCP │ Webhooks │ Accelerators │ AI    │\n└──────────────────────────────────────────────────┘\n```\n\n---\n\n## 3. The Three Data Flows\n\nThree distinct data flows with hard boundaries:\n\n### Flow A — Structured / Truth\n\n```\nTools → Loader → Normalizer → Spine\n                                 ↓\n                         Actions on tools\n                                 ↓\n                         (flows back into Flow A — REPEAT LOOP)\n```\n\n- Source: SaaS connectors (CRM, billing, support, etc.)\n- Destination: The Spine (structured truth)\n- Has a **repeat loop**: governed actions executed on tools flow back as new structured data\n- This is the ONLY flow with a repeat loop\n\n### Flow B — Unstructured / Context\n\n```\nDocs, emails, conversations → Context Store + Spine linking\n```\n\n- Source: Documents, emails, Slack messages, meeting transcripts\n- Destination: Context Store, linked to Spine entities\n- NO repeat loop\n- Enriches entities with qualitative context\n\n### Flow C — AI Knowledge / Memory\n\n```\nAI sessions → Triage Bot (SOLE writer) → Memory Store\n```\n\n- Source: AI interactions, Twin sessions, user conversations\n- Writer: Triage Bot is the SOLE writer to memory\n- Twin can also write Truth + Context summaries via Triage Bot\n- Read access: per tenant OAuth only\n- Grows daily — accumulated intelligence\n- NO repeat loop\n- **NEVER writes directly to the Spine** — only via HITL approval\n\n### Critical Boundaries\n\n| Property        | Flow A     | Flow B        | Flow C                |\n| --------------- | ---------- | ------------- | --------------------- |\n| Data type       | Structured | Unstructured  | AI-generated          |\n| Destination     | Spine      | Context Store | Memory Store          |\n| Repeat loop     | YES        | NO            | NO                    |\n| Writes to Spine | Direct     | Linked        | NEVER (only via HITL) |\n| Trust level     | Verified   | Contextual    | Requires approval     |\n\n---\n\n## 4. L1 — The Workspace (12 Domain Views)\n\nEach domain view is schema-filtered and provides role-specific interfaces.\n\n| #   | Domain              | Icon | Files | Views             | Entity Types | Notes                                                  |\n| --- | ------------------- | ---- | ----- | ----------------- | ------------ | ------------------------------------------------------ |\n| 1   | Account Success     | 💚   | 49    | 20 active         | 18           | Most feature-rich domain                               |\n| 2   | BizOps              | ⚙️   | 27    | 7 + C-suite views | 14           | CEO/COO/CIO/Founder views                              |\n| 3   | Finance             | 💰   | 20    | 7                 | 15           | Revenue, billing, forecasting                          |\n| 4   | IT Admin            | 🔧   | 31    | 6                 | 12           | System management                                      |\n| 5   | Marketing           | 📢   | 16    | 8                 | 14           | Campaigns, attribution                                 |\n| 6   | Personal            | 👤   | 10    | 8                 | 7            | Waitlisted for launch (M1-6)                           |\n| 7   | Procurement         | 📦   | 11    | 6                 | 11           | Vendor management                                      |\n| 8   | Product Engineering | 💻   | 14    | 7                 | 16           | Roadmap, sprints, releases                             |\n| 9   | RevOps              | 📈   | 8     | 8                 | 14           | Most analytically sophisticated                        |\n| 10  | SalesOps            | 🎯   | 5     | 8                 | 14           | Pipeline, forecasting                                  |\n| 11  | Service             | 🎧   | 11    | 6                 | 12           | Support, SLA, escalation                               |\n| 12  | Student-Teacher     | 🎓   | —     | —                 | —            | Shell only (0 bytes, dashboard wired, not in DomainId) |\n\n### Source Locations\n\n- Domain implementations: `apps/web/src/components/l1/domains/`\n- Domain type configs: `apps/web/src/components/l1/domains/domain-types.ts`\n- Schema definitions: `packages/types/src/schema.ts` (DOMAIN_SPINE_CONFIG)\n\n---\n\n## 5. L2 — The Cognitive Layer (14 Components)\n\nAccessible via `Cmd+J`. Two overlay implementations exist in the codebase:\n\n| #   | Component                 | Purpose                                       |\n| --- | ------------------------- | --------------------------------------------- |\n| 1   | SpineUI                   | View and interact with Spine data             |\n| 2   | ContextUI                 | Browse unstructured context                   |\n| 3   | KnowledgeUI               | Access knowledge memory                       |\n| 4   | Evidence Drawer           | Supporting evidence for signals               |\n| 5   | Signals                   | AI-generated insights (from Think layer)      |\n| 6   | Think (Active Situations) | Situation awareness, pattern detection        |\n| 7   | Act                       | Agent execution (Twin lives here)             |\n| 8   | HITL / Approvals          | Human-in-the-loop approval queue              |\n| 9   | Govern                    | Governance rules and boundaries               |\n| 10  | Adjust                    | Configuration and tuning                      |\n| 11  | Repeat                    | Loop monitoring and status                    |\n| 12  | Audit Trail (LayerAudit)  | Full audit log of all actions                 |\n| 13  | Agent Config              | Configure agent behaviors                     |\n| 14  | Digital Twin              | Personal AI agent with read-only Spine access |\n\n### Important Notes\n\n- Signals are AI Insights generated in the Think layer — NOT raw events from connectors\n- Agents (including Twin) live ONLY in Act, not in truth formation\n- Twin has READ-ONLY access to Spine; can only write via HITL approval\n- Two overlay implementations exist: `intelligence-overlay-new.tsx` (bottom-sheet) and `cognitive/CognitiveLayer.tsx` (sliding panel, 13 tabs)\n\n---\n\n## 6. The Schema System\n\nThe schema system is IntegrateWise's real moat — runtime composability per tenant.\n\n### How It Works\n\n```\ngetSpineConfig(industry, department) → unique schema per tenant\n```\n\n- 12 domain schemas × 11 industry overlays = combinatorial configuration\n- Schema controls EVERYTHING downstream: loader extraction, normalizer filtering, L1 views, L2 cognitive scope\n\n### 11 Industry Overlays\n\nSaaS, Healthcare, Manufacturing, Automotive, Retail, Financial Services, Logistics, Media & Entertainment, Public Sector, Education, Professional Services\n\n### Authoritative Sources\n\n| File                                               | Lines | Content                                            |\n| -------------------------------------------------- | ----- | -------------------------------------------------- |\n| `packages/types/src/schema.ts`                     | 2113  | `DOMAIN_SPINE_CONFIG` — 12 domains (authoritative) |\n| `packages/types/src/adaptive-schema.ts`            | —     | 10 domains (DRIFT — missing 2)                     |\n| `sql-migrations/050_adaptive_spine_12_domains.sql` | 1130  | Database schema for all 12 domains                 |\n\n### Known Drift\n\n- `adaptive-schema.ts` only defines 10 of 12 domains (missing Procurement and Student-Teacher)\n- `domain-types.ts` spineProjection — resolved, useHydrateProjection routes correctly\n\n---\n\n## 7. Entity 360 — Convergence Point\n\nEntity 360 is where all three data flows converge:\n\n```\nFlow A (Structured Truth)     ──┐\nFlow B (Unstructured Context) ──┼──→ Entity 360\nFlow C (AI Knowledge/Memory)  ──┘\n                                       ↓\n                                 Twin activates here\n                                 (READ-ONLY access to Spine)\n```\n\n- Entity 360 requires cross-source data to be meaningful\n- You CANNOT \"connect one system and see Entity 360\" — this was a doc error\n- Twin can only write to Spine via HITL approval from this context\n\n---\n\n## 8. The Cognitive Loop\n\n```\nThink → Act → Govern → Repeat → Adjust\n  ↑                                 │\n  └─────────────────────────────────┘\n```\n\n| Stage  | What Happens                                              |\n| ------ | --------------------------------------------------------- |\n| Think  | Pattern detection, signal generation, situation awareness |\n| Act    | Agent execution — Twin and other agents live here         |\n| Govern | Rule enforcement, trust boundaries, compliance checks     |\n| Repeat | Loop execution on structured data (Flow A only)           |\n| Adjust | System tuning, confidence calibration, feedback loops     |\n\n### Critical: Where Agents Live\n\n- Agents (including Twin) live ONLY in Act\n- Agents do NOT participate in truth formation\n- All agent outputs go through Govern before affecting the Spine\n\n---\n\n## 9. Connector Ecosystem\n\n### Connector Types\n\n| Type            | Description                         | Examples                                  |\n| --------------- | ----------------------------------- | ----------------------------------------- |\n| SaaS Connectors | Standard business tool integrations | Salesforce, HubSpot, Stripe, Zendesk      |\n| MCP Connectors  | Model Context Protocol integrations | Knowledge base, Figma                     |\n| Webhooks        | Event-driven integrations           | Custom event sources                      |\n| Accelerators    | Pre-built domain packages           | Industry-specific starter configs         |\n| AI Connectors   | AI service integrations             | ChatGPT, Claude, Gemini, Perplexity, Grok |\n\n### Key Principles\n\n- **\"Every input is a connector\"** — unified ingestion model\n- **Auto-upgrade system**: child connectors inherit upgrades from parent connectors\n- **Purchase decision entry point**: users check connector availability first\n- **Only claim production-verified count**: 4-point verification (OAuth flow, creamy load, field mapping, delta sync)\n- Connector count at launch: state only what passes verification (DO NOT claim \"50+\")\n\n### Credential Storage\n\n- Tokens ARE stored encrypted in `connector_credentials`\n- Previous docs said \"No credential storage\" — this was FALSE and must be corrected\n- Correct framing: \"Credentials are encrypted at rest, scoped per tenant, with OAuth refresh rotation\"\n\n---\n\n## 10. The Knowledge Memory\n\nThis is what makes IntegrateWise a \"Knowledge Workspace\":\n\n- Accumulated intelligence that grows daily\n- No retraining needed — context is always current\n- Triage Bot is the sole writer to memory\n- Per-tenant OAuth scoping for read access\n- Twin reads verified memory, writes back summaries via Triage Bot\n\n### Why It Matters\n\nTraditional AI tools lose context between sessions. IntegrateWise's Knowledge Memory:\n\n- Remembers every verified interaction\n- Builds organizational knowledge over time\n- Provides the Twin with historical context\n- Never requires manual knowledge base maintenance\n\n---\n\n## 11. Trust & Governance\n\n### The TruthLayer\n\nTruthLayer is a **platform capability**, not a standalone product.\n\nHow it works:\n\n1. AI generates output (entity extraction, recommendations, summaries)\n2. Triage Bot processes: confidence scoring, conflict detection\n3. Results go to Human Approval queue\n4. Approved items become verified memory\n5. Twin reads verified memory at Entity 360\n\n### HITL (Human-in-the-Loop)\n\n- Every AI action that affects the Spine requires human approval\n- Three levels: auto-approve (high confidence), review (medium), block (low/conflict)\n- Approval queue visible in L2 Cognitive Layer\n\n### Trust Boundary\n\n- Flow A and B write directly to their stores (Spine, Context Store)\n- Flow C NEVER writes directly to Spine\n- The boundary between AI-generated and verified data is absolute\n\n---\n\n## 12. 20 Products Across 3 Surfaces\n\n### Surface 1: Account Success (8 Products)\n\n**No Twin:**\n\n- DataSentinel — Data quality monitoring\n- VaultGuard — Compliance and audit\n- ArchitectIQ — Solution architecture\n- TemplateForge — Template management\n\n**Basic Twin:**\n\n- SuccessPilot — CS automation\n- DealDesk — Deal management\n\n**Full Twin + TruthLayer:**\n\n- ChurnShield — Churn prediction and prevention\n- SuccessCommand — Executive CS dashboard\n\n### Surface 2: Business Ops (7 Products)\n\n**No Twin:**\n\n- ComplianceVault — Regulatory compliance\n- VendorGuard — Vendor management\n- PartnerBridge — Partner ecosystem\n\n**Basic Twin:**\n\n- GrowthDesk — Growth analytics\n- HirePilot — Hiring automation\n\n**Full Twin + TruthLayer:**\n\n- FinPulse — Financial intelligence\n- OpsCore — Operations command center\n\n### Surface 3: Personal Space (5 Products)\n\n**WAITLISTED for M1-6 launch. CTA: \"Join the Waitlist\"**\n\n**No Twin:**\n\n- WealthPilot — Personal finance\n- WellnessCore — Health and wellness\n\n**Basic Twin:**\n\n- LearningDesk — Learning management\n- RelationshipMap — Professional network\n\n**Full Twin + TruthLayer:**\n\n- LifeOps — Personal operations hub\n\n---\n\n## 13. Founding Story\n\n1. Nirmal was a CSM (Customer Success Manager)\n2. Experienced the Human API problem firsthand — being the bridge between disconnected tools\n3. Built the Spine (intelligent plumbing) which saved an $8M account\n4. Multiple other proofs: support cases solved, unresolved issues resolved\n5. Proposed organization-wide implementation\n6. Superiors tried to grab the idea\n7. Realized the opportunity was bigger — started exploring independently\n8. Started as **Mule Nexus** in 2024, evolved into **IntegrateWise**\n9. \"Depth matters\" — Depth Matrix stays as a concept\n\n---\n\n## 14. Go-To-Market (Current Phase)\n\n### M1-3: Founder-Led Sales\n\n| Element        | Value                               |\n| -------------- | ----------------------------------- |\n| CTA            | \"Book a Demo\" / \"Join Early Access\" |\n| Model          | Founder-led sales (NOT self-serve)  |\n| Personal Space | Waitlisted (not live)               |\n| Pricing tiers  | Starter, Growth, Command            |\n\n### What NOT to Say on the Website\n\n- \"Start Free\" / \"Start Free Trial\" (not until M3-6)\n- \"No credit card required\"\n- \"Connect in 2 minutes\"\n- \"50+ integrations\" (only claim verified count)\n- Self-serve signup flow references\n\n### CTA Progression\n\n| Phase | CTA              | Model       |\n| ----- | ---------------- | ----------- |\n| M1-3  | Book a Demo      | Founder-led |\n| M3-6  | Start Free Trial | Guided PLG  |\n| M6+   | Start Free       | Full PLG    |\n\n---\n\n## 15. Architectural Review (9.2/10)\n\n### Strengths\n\n- **Schema-driven architecture** — real moat, runtime composability per tenant\n- **Three-flow separation** with hard boundaries — clean data trust model\n- **Trust/governance model** — Triage Bot + HITL + tenant OAuth\n- **Continuous loop** via Flow A — the only flow with repeat\n- **Knowledge memory accumulation** — commercial moat that grows daily\n\n### Issues (Code-Level, Not Documentation)\n\n| Issue                                   | Location                                               | Impact                                                              |\n| --------------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------- |\n| spineProjection (resolved)              | `domain-types.ts`                                      | Resolved — useHydrateProjection routes correctly for all 12 domains |\n| Schema duplication                      | `schema.ts` vs `adaptive-schema.ts`                    | 12 vs 10 domains                                                    |\n| Two competing L2 overlays               | `intelligence-overlay-new.tsx` vs `CognitiveLayer.tsx` | UX inconsistency                                                    |\n| Account Success disproportionately deep | 49 files vs 5-16 for others                            | Coverage gap                                                        |\n| Student-Teacher shell empty             | 0 bytes, not registered in DomainId                    | Incomplete domain                                                   |\n\n---\n\n## 16. Documentation Rules — Public vs Internal\n\n### What Public Docs SHOULD Cover\n\n- The product story (Human API problem → Turning Point → Solution)\n- The Workspace (what users see, role-based views, schema-driven)\n- The Spine (intelligent plumbing, what it connects, adaptive, grows with you)\n- The Cognitive Layer (overlay experience, not internals)\n- Three Data Flows (at PRODUCT level, not architecture level)\n- Knowledge Memory (accumulated intelligence, no retraining)\n- Connectors (purchase decision page + auto-upgrade + types)\n- Who It's For (founders, CS, sales, finance, product, analysts)\n- Trust & governance (truth boundary, approval-driven, HITL)\n\n### What Public Docs MUST NOT Expose\n\n- 8-stage pipeline internals\n- Normalizer stages (S1-S8, S7.5)\n- Hydration buckets (B0-B7), \"creamy load\"\n- Twin trigger engine mechanics (10 triggers, guardrails, scoring)\n- Identity resolution internals\n- Worker-level architecture (Cloudflare Workers, D1, KV, queues)\n- Firebase SMB architecture\n- Any backend processing details — the backend is infrastructure, NOT the product\n\n### Errors in Previous Public Docs (All Fixed in Rewrite)\n\n| Error                                       | Correction                                         |\n| ------------------------------------------- | -------------------------------------------------- |\n| Homepage tagline \"System of Context\"        | Use \"Knowledge Workspace\"                          |\n| Hero CTA \"Get Started\"                      | \"Book a Demo\"                                      |\n| Getting Started describes self-serve signup | Remove — no self-serve at launch                   |\n| \"Connect first system, see Entity 360\"      | Entity 360 needs cross-source data                 |\n| \"50+ business systems\"                      | Only claim production-verified count               |\n| \"No credential storage\"                     | Tokens stored encrypted in `connector_credentials` |\n| \"Bi-directional sync\"                       | Governed action execution                          |\n| Custom Connector SDK referenced             | Doesn't exist                                      |\n| Solutions: 5 role pages                     | Align to \"Who It's For\" framing                    |\n| Technical pipeline details in public docs   | Move to internal                                   |\n\n---\n\n## 17. Writing Style\n\n### Voice & Tone\n\n- Authoritative but approachable\n- Second-person (\"you\")\n- Active voice\n- Product-first, not tech-first\n- No emojis in prose\n\n### Page Structure\n\nEvery page must have:\n\n```markdown\n---\ntitle: Page Title\nslug: /section/page-slug\nsummary: One-sentence summary\naudience: [public | internal | team]\nstatus: [draft | review | published]\nowner: nirmal\nlastReviewed: 2026-04-09\npublishEligible: true\ntags: [relevant, tags]\n---\n\n# Page Title\n\nOpening statement (1-2 sentences).\n\n> Blockquote principle (where appropriate)\n\n## Section Heading\n\nContent...\n\n## Next Steps\n\n- [Link to next page](/section/next-page)\n- [Link to related page](/section/related-page)\n```\n\n### Formatting Conventions\n\n- ASCII diagrams for architecture (not images)\n- Tables for comparisons\n- VitePress containers (`::: tip`, `::: info`, `::: warning`) used sparingly\n- Five Core Principles referenced throughout where appropriate\n\n---\n\n## 18. Sidebar Structure — Public Docs\n\n```\nThe Story (3 pages)\n├── Why Work Is Broken         /story/why-work-is-broken\n├── The Turning Point          /story/the-turning-point\n└── What Is IntegrateWise      /story/what-is-integratewise\n\nThe Workspace (4 pages)\n├── How It Works               /workspace/how-it-works\n├── Domain Views               /workspace/domain-views\n├── Entity 360                 /workspace/entity-360\n└── Day One Experience         /workspace/day-one\n\nThe Spine (5 pages)\n├── What the Spine Is          /spine/what-the-spine-is\n├── What It Connects           /spine/what-it-connects\n├── Adaptive by Design         /spine/adaptive-by-design\n├── Grows with You             /spine/grows-with-you\n└── The Truth Boundary         /spine/truth-boundary\n\nThe Cognitive Layer (6 pages)\n├── How the Overlay Works      /cognitive-layer/how-the-overlay-works\n├── Spine, Context & Knowledge /cognitive-layer/spine-context-knowledge-ui\n├── The Twin                   /cognitive-layer/the-twin\n├── Signals & Think            /cognitive-layer/signals-and-think\n├── Approval-Driven Execution  /cognitive-layer/approval-driven-execution\n└── The Continuous Loop        /cognitive-layer/the-continuous-loop\n\nThree Data Flows (3 pages)\n├── Structured Truth           /data-flows/structured-truth\n├── Unstructured Context       /data-flows/unstructured-context\n└── AI Knowledge & Memory      /data-flows/ai-knowledge-memory\n\nThe Knowledge Memory (3 pages)\n├── How Memory Works           /knowledge-memory/how-memory-works\n├── Why Knowledge Workspace    /knowledge-memory/why-knowledge-workspace\n└── No Retraining Needed       /knowledge-memory/no-retraining-needed\n\nConnectors & Integrations (4 pages)\n├── Overview                   /connectors/overview\n├── How Connectors Work        /connectors/how-connectors-work\n├── Auto-Upgrade               /connectors/auto-upgrade\n└── Request a Connector        /connectors/request-a-connector\n\nWho It's For (4 pages)\n├── Founders & Leaders         /who-its-for/founders-and-leaders\n├── Revenue & Customer Teams   /who-its-for/revenue-and-customer-teams\n├── Operations & Finance       /who-its-for/operations-and-finance\n└── Product & Engineering      /who-its-for/product-and-engineering\n\nReference (3 pages)\n├── Glossary                   /reference/glossary\n├── Depth Matrix               /reference/depth-matrix\n└── FAQ                        /reference/faq\n```\n\n---\n\n## 19. Known Issues (Code, Not Docs)\n\nThese are codebase issues identified during architectural review. They do NOT affect documentation content but should be tracked for engineering.\n\n1. `spineProjection` — resolved, `useHydrateProjection` routes correctly for all 12 domains\n2. **Schema duplication** — `schema.ts` (12 domains) vs `adaptive-schema.ts` (10 domains, missing Procurement + Student-Teacher)\n3. **Two competing L2 overlay implementations** — `intelligence-overlay-new.tsx` (bottom-sheet) and `cognitive/CognitiveLayer.tsx` (sliding panel, 13 tabs)\n4. **Account Success disproportionately deep** — 49 files, 20 views vs 5-16 files for other domains\n5. **Student-Teacher domain shell empty** — 0 bytes, dashboard wired but not registered in DomainId enum\n\n---\n\n## 20. Key Source Files\n\n### Product Content Sources\n\n| File                                         | Purpose                                |\n| -------------------------------------------- | -------------------------------------- |\n| `docs/gtm/POSITIONING_FRAMEWORK.md`          | Approved positioning, always/never say |\n| `docs/gtm/LAUNCH_PHASE_ADDENDUM.md`          | Launch overrides, CTA rules            |\n| `docs/product/PRODUCT_CATALOG_20.md`         | 20 products across 3 surfaces          |\n| `docs/product/PRODUCT_LAYERS_BY_ROLE.md`     | Role-based views                       |\n| `docs/product/PLATFORM_FEATURES_COMPLETE.md` | Full feature inventory                 |\n\n### Architecture Sources\n\n| File                                                 | Purpose                              |\n| ---------------------------------------------------- | ------------------------------------ |\n| `packages/types/src/schema.ts`                       | 12 domain schemas (AUTHORITATIVE)    |\n| `packages/types/src/adaptive-schema.ts`              | Adaptive schema (DRIFT — 10 domains) |\n| `apps/web/src/components/l1/domains/`                | All 12 domain view implementations   |\n| `apps/web/src/components/l2/`                        | All 14 L2 cognitive components       |\n| `apps/web/src/components/l1/domains/domain-types.ts` | Domain configs                       |\n| `sql-migrations/050_adaptive_spine_12_domains.sql`   | Database schema                      |\n\n### VitePress Config\n\n| File                        | Purpose                      |\n| --------------------------- | ---------------------------- |\n| `docs/.vitepress/config.ts` | Main VitePress configuration |\n| `docs/internal/_sidebar.ts` | Internal docs sidebar        |\n| `scripts/sync-docs.sh`      | Sync from live repo to docs  |\n\n---\n\n_End of Architecture Context. This document is the single source of truth for all documentation decisions._\n"}