{"slug":"business/CANONICAL_TAXONOMY","title":"IntegrateWise — Canonical Taxonomy (FINAL)","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/CANONICAL_TAXONOMY.mdx","bytes":6793,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Version:** 1.0 | **Date:** 2026-06-09 | **Status:** Canonical — locked\n> **Authority:** Nirmal (Founder)\n> **Rule:** These four path-series are orthogonal. Never collapse them into one\n> layer-number hierarchy. Each answers a different question.\n\nThere is **one platform** seen through **four orthogonal paths**. A surface (S),\na stage (U), a render (V), and a self-run loop (CZ) can all describe the same\nmoment — they are not the same axis. Use the right prefix for the right question.\n\n```\nS-series  System Architecture     \"how is the platform built?\"   (surfaces)\nU-series  Human Operating Model   \"what is the human doing?\"      (cognitive stages)\nV-series  View Path               \"how is information rendered?\"  (render modes)\nCZ-series Customer Zero Path      \"how does IW run itself?\"       (self-operation loop)\n```\n\n> Supersedes prior numbering: the earlier \"H-series\" Human Operating Model is\n> renamed to **U-series**. The \"L0–L4\" UI layers are the **S-series** (the\n> product surface table renders S1–S4 as L1–L4 — same thing; prefer S going forward).\n\n---\n\n## S-series — System Architecture (how IntegrateWise is built)\n\n```\nS0 Infrastructure   Nango · Connector-sync · Loader · Normalizer · Spine ·\n                    Main Memory · Spine Cache · Continuity Bridge (Gateway · ADK · Auth)\n                    — invisible to users.\n\nS1 Workspace        Owner: IntegrateWise\n                    Purpose: DO WORK\n                    /desk · /entity360 · /inbox · /build · /run · /grow · /tasks ·\n                    /horizon · /decide · /react · 12 domain views\n                    Contains: Desk · Inbox · Entity360 · Tasks · Pipeline · Projects ·\n                    Reports · Approvals · Actions · Triage · Domain Views\n                    This is where users spend their day. OWUI never owns this.\n\nS2 Awareness        Owner: IntegrateWise\n                    Purpose: NOTICE\n                    Drawer · Signals · Scoring · Predictions · Insights · Evidence ·\n                    Lineage · Readiness · Triage · Governance Queue\n                    THIS IS THE MOAT. If IW disappears and only OWUI remains,\n                    signals, scoring, predictions, entity awareness, and governance\n                    all disappear. The intelligence lives here, not in the chat.\n\nS3 Twin             Owner: Open WebUI (runtime) + IntegrateWise (intelligence via Bridge)\n                    Purpose: THINK\n                    Open WebUI · Agent Zero · Grok-4.3 · x.ai voice \"eve\" ·\n                    MCP tools · Reasoning · Planning · Playbooks · Briefings\n                    The Twin is the CONVERSATION LAYER for the Spine.\n                    Not the source of truth. Not the governance system.\n                    Not the memory system. Just the reasoning surface.\n\nS4 Library          Owner: IntegrateWise\n                    Purpose: KNOW\n                    Coda · Org Memory · Personal Memory · Book of Projects ·\n                    Doctrine · Decisions · Research · Knowledge Assets\n                    The permanent memory substrate.\n                    The Twin reads from it. The Twin does not own it.\n```\n\n> The product surface table (L1–L4) = S1–S4. All surfaces read from Spine Cache.\n> Open WebUI powers the Twin. IntegrateWise powers the intelligence.\n> See: `docs/tech/LAYER_OWNERSHIP_AND_TWIN_RUNTIME.md` for full ownership doctrine.\n\n---\n\n## U-series — Human Operating Model (what the human does)\n\n```\nU1 Work       User operating              CRM · Projects · Campaigns · Operations\nU2 Notice     Twin notices                Risk · Opportunity · Change · Alert\nU3 Reason     User engages Twin           Why? · What changed? · What should we do?\nU4 Decide     Governance                  Approve · Reject · Delegate · Escalate\nU5 Act        Execution                   Playbook · Workflow · Agent · Human action\nU6 Remember   Memory creation             Decision · Commitment · Learning · Policy → Memory\n```\n\n---\n\n## V-series — View Path (how information is rendered)\n\n```\nV1 Operational   tables, queues, lists, KPI strips (work data)\nV2 Entity        Entity 360 assembly (Spine ∩ Memory ∩ Signals)\nV3 Awareness     signal cards, drawer overlays, presence\nV4 Reasoning     reasoning stream, proposals, evidence\nV5 Governance    proposal queue, decision ledger, audit lineage\nV6 Execution     task trees, tool-call logs, playbook status\nV7 Knowledge     library tree/graph/node, memory browser, lineage\n```\n\n---\n\n## CZ-series — Customer Zero Path (how IntegrateWise runs itself)\n\n```\nCZ1 Build      build the product (this repo, the agents, the pipeline)\nCZ2 Operate    run ops on IW itself (integratewise-ops, the Twin, the vault)\nCZ3 Sell       GTM, positioning, pipeline — IW selling IW\nCZ4 Deliver    onboarding, success, the Continuity Bridge in customers' hands\nCZ5 Learn      capture decisions/learnings into governed memory\nCZ6 Improve    promote learnings → doctrine → next iteration\n```\n\n---\n\n## Cross-mapping (orthogonal — a row is \"primarily supports\", not \"equals\")\n\n```\nSYSTEM (S)          USER (U)         VIEW (V)              CUSTOMER ZERO (CZ)\nS1 Workspace    →   U1 Work      →   V1 Operational / V2 Entity   →   CZ2 Operate\nS2 Awareness    →   U2 Notice    →   V3 Awareness                 →   CZ2 Operate\nS3 Twin         →   U3 Reason    →   V4 Reasoning                 →   CZ1/CZ3/CZ5\n(governance)    →   U4 Decide    →   V5 Governance                →   CZ5 Learn\n(execution)     →   U5 Act       →   V6 Execution                 →   CZ4 Deliver\nS4 Library      →   U6 Remember  →   V7 Knowledge                 →   CZ6 Improve\n```\n\n---\n\n## Governance, stated in the locked vocabulary\n\n```\nApproval is the U4 Decide stage.\nIts UI is surfaced on the S2 Awareness surface (rendered as V5 Governance).\nIt is NEVER performed in the S3 Twin chat — chat is not an audit trail.\nThe Twin (U3 Reason on S3) only PROPOSES. It never Decides (U4) or Acts (U5).\n```\n\nEquivalent to the product-table note: _\"Approval UI lives in L2 (=S2 Awareness)\nonly — never in L3 (=S3 Twin) chat.\"_\n\n---\n\n## The Rule (locked)\n\n```\nS = System surfaces      ·  use for \"where / what surface\"\nU = Human stages         ·  use for \"what is the human doing\"\nV = Render modes         ·  use for \"how is it displayed\"\nCZ = Self-operation loop ·  use for \"how IW runs itself\"\n\nNever describe a cognitive stage with an S number.\nNever describe a surface with a U number.\nNever describe a render mode with S or U.\nOne platform. Four orthogonal views.\n```\n\n---\n\n_One platform, four paths. System builds it. Users operate it. Views render it.\nCustomer Zero proves it._\n"}