{"slug":"architecture/SPINEWORKSPACE_CANONICAL_PRODUCT_MANUAL","title":"SpineWorkspace — Canonical Product Manual","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/SPINEWORKSPACE_CANONICAL_PRODUCT_MANUAL.md","bytes":16717,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **THE DEFINITIVE END-STATE MODEL**\n> This document is the frozen source of truth for all architecture, product, frontend, schema, and narrative decisions.\n> **SUPERSEDED BY FOUNDER CANON** for product/experience semantics. See `docs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` (31 August 2026) as the authoritative source.\n\n---\n\n## The Tier-0 Principle\n\n> **Business Context is the semantic foundation of SpineWorkspace.** It connects organizational business reality to Work, Humans, AI, Agents, Memory, Knowledge, Capabilities, Communication, Decisions, Governance, Execution, Evidence, Continuity and Outcomes. Without Business Context, SpineWorkspace has no meaning; it becomes another collection of tools and interfaces.\n>\n> **The Spine gives work its business context.**\n\n---\n\n## The Final Doctrine\n\n> **IntegrateWise provides the infrastructure substrate. SpineWorkspace provides the business operating environment. Business Context is THE semantic foundation. The Business Context Spine IS the organization's memory — the connected representation of entities, work, state, relationships, events, decisions, evidence, provenance and memory. Each user receives an authorized projection of that organizational context through the Human Workbench, while their Twin operates in the AI Workbench to help understand, allocate, coordinate and execute work. The Communication Bridge enables governed exchange between Spine, humans, Twins, agents, workflows and connected systems through the appropriate runtime and communication mechanisms. Actions execute against the systems that remain authoritative, results are re-ingested and reconciled, loop state is updated, and validated outcomes become organizational memory and knowledge for the next work.**\n\n---\n\n## Deepest Abstraction\n\n```text\nBUSINESS CONTEXT\n      ↓\n    WORK\n      ↓\n  HUMAN + AI\n      ↓\n  EXECUTION\n      ↓\nRECONCILIATION\n      ↓\n  KNOWLEDGE\n      ↓\n  NEXT WORK\n```\n\n**Spine preserves continuity across the entire loop.**\n\n---\n\n## The Final 18-Layer Stack\n\n| Layer | Canonical Concept              |\n| ----- | ------------------------------ |\n| 0     | Organization                   |\n| 1     | Goals / Needs / Objectives     |\n| 2     | Business Context               |\n| 3     | Context Ingestion & Synthesis  |\n| 4     | Business Context Spine         |\n| 5     | Organizational Memory          |\n| 6     | Work Graph                     |\n| 7     | Projection & Context Assembly  |\n| 8     | Human Workbench                |\n| 9     | AI Workbench (Twin + Agents)   |\n| 10    | Work Allocation                |\n| 11    | Governance                     |\n| 12    | Communication Bridge           |\n| 13    | ADK / Orchestrator / ACP / MCP |\n| 14    | Agent Fabric                   |\n| 15    | Execution Fabric               |\n| 16    | Source Systems                 |\n| 17    | Re-ingestion                   |\n| 18    | Reconciliation                 |\n| 19    | Loop State                     |\n| 20    | Memory / Knowledge Promotion   |\n| 21    | Next Work                      |\n\n---\n\n## Master Diagram\n\n```text\n                         ORGANIZATION\n                              │\n                              ▼\n                     GOALS / NEEDS / OBJECTIVES\n                              │\n                              ▼\n                      BUSINESS CONTEXT\n                              │\n             ┌────────────────┴────────────────┐\n             │                                 │\n      PEOPLE / RESPONSIBILITIES        BUSINESS SYSTEMS\n             │                                 │\n             └────────────────┬────────────────┘\n                              ▼\n                    CONTEXT INGESTION\n                              │\n             ┌────────────────┴────────────────┐\n             │                                 │\n       Pre-processing                    Discovery\n       Normalization                     Connectors\n       Entity Resolution                 Events\n       Classification                    Files\n       Synthesis                         APIs\n             │                                 │\n             └────────────────┬────────────────┘\n                              ▼\n                   BUSINESS CONTEXT SPINE\n                              │\n             ┌────────────────┼────────────────┐\n             │                │                │\n      Canonical Context   Work Graph      Org Memory\n             │                │                │\n             ├────────────────┼────────────────┤\n             │                │                │\n          State          Decisions         Evidence\n             │                │                │\n             └────────────────┼────────────────┘\n                              ▼\n                   PROJECTION / CONTEXT ASSEMBLY\n                              │\n              ┌───────────────┴────────────────┐\n              │                                │\n       HUMAN WORKBENCH                   AI WORKBENCH\n              │                                │\n              │          Twin + Agents         │\n              │                                │\n              └─────────────┼──────────────────┘\n                            ▼\n                         WORK\n                            │\n                     WORK ALLOCATION\n                            │\n              ┌─────────────┼─────────────┐\n              │             │             │\n           HUMAN          TWIN         AGENT\n              │             │             │\n              └─────────────┼─────────────┘\n                            ▼\n                       GOVERNANCE\n                            │\n                            ▼\n                   COMMUNICATION BRIDGE\n                            │\n             Spine + ADK + Orchestrator + ACP\n                            │\n                 ┌──────────┼──────────┐\n                 │          │          │\n                MCP      Workflows    APIs\n                 │          │          │\n                 └──────────┼──────────┘\n                            ▼\n                    EXECUTION FABRIC\n                            │\n                            ▼\n                    SOURCE SYSTEMS\n                            │\n                            ▼\n                     RESULT / EVENT\n                            │\n                            ▼\n                     RE-INGESTION\n                            │\n                            ▼\n                    RECONCILIATION\n                            │\n                            ▼\n                    LOOP STATE UPDATE\n                            │\n                            ▼\n                  BUSINESS CONTEXT SPINE\n                            │\n                            ▼\n                         KNOWLEDGE\n                            │\n                            ▼\n                       NEXT WORK\n```\n\n---\n\n## Company vs Product\n\n### IntegrateWise — Company + Platform Infrastructure\n\n```text\nIdentity\nConnectivity\nAI Infrastructure\nAgent Runtime\nCommunication\nGovernance\nExecution Infrastructure\nDeveloper Platform\nConnector Ecosystem\n```\n\n### SpineWorkspace — Customer Product / Operating Environment\n\n```text\nBusiness Context\nBusiness Context Spine\nWork\nWork Graph\nProjections\nHuman Workbench\nAI Workbench\nTwin + Spine Agents\nOrganizational Memory\nWork Allocation\nDomain Work\nBusiness KPIs\nCommunications\nExecution\nReconciliation\nContinuity\n```\n\n---\n\n## Critical Architectural Boundaries\n\n### Canonical → Operational Boundary (INVARIANT)\n\n```text\n                 SPINE\n                   │\n          ┌────────┴────────┐\n          │                 │\n      CANONICAL          PROJECTION\n      TRUTH                │\n          │                ▼\n          │         CONTEXT ASSEMBLY\n          │                │\n          │                ▼\n          │             SANDBOX /\n          │         OPERATIONAL CONTEXT\n          │                │\n          └───────┐    ┌───┘\n                  │    │\n                HUMAN  AI\n                       │\n                       TWIN\n                       │\n                     AGENTS\n```\n\n**AI does NOT receive unrestricted canonical organizational memory.**\n\n```text\nCanonical Spine\n      ↓\nAuthorized Projection\n      ↓\nContext Assembly\n      ↓\nOperational Context / Sandbox\n      ↓\nTwin / Agent\n```\n\n### Twin Scope\n\n- Twin is the **sole user-facing orchestrator**\n- Operates in the **AI Workbench**\n- Works **WITH** human, not **instead of**\n- Receives authorized projections only\n- Operates on Business Context, not raw data\n\n### AI Workbench Scope\n\n```text\nHuman\n  ↓\nHuman Workbench\n  ↓\nBusiness Context\n  ↓\nAI Workbench\n  │\n  ├── Twin\n  │   ├── Business Context Understanding\n  │   ├── Work Allocation\n  │   ├── Agent Coordination\n  │   └── Governance\n  │\n  └── Spine Agents\n      ├── Domain Agents\n      ├── Specialist Agents\n      ├── Research Agents\n      └── Workflow Agents\n```\n\n**Twin coordinates work; Agents execute bounded tasks on Business Context.**\n\n---\n\n## Work Graph\n\nWork is the **primary coordination unit** (not tasks).\n\n```text\nBUSINESS GOAL\n      ↓\n    WORK\n      ↓\nWORK GRAPH\n  │\n  ├── Tasks\n  ├── Decisions\n  ├── Actions\n  ├── Communications\n  ├── Approvals\n  ├── Dependencies\n  ├── Exceptions\n  ├── Human activity\n  └── AI activity\n```\n\n---\n\n## Work Allocation\n\nFor every piece of work:\n\n```text\nWHAT NEEDS TO HAPPEN?\n        ↓\nWHO / WHAT SHOULD DO IT?\n```\n\nDecision factors:\n\n```text\nCapability · Authority · Responsibility · Risk · Complexity\nContext · Urgency · Cost · Availability · Policy\nHuman preference · Historical performance\n```\n\nPossible allocation:\n\n```text\nHUMAN · AI/TWIN · SPECIALIST AGENT · WORKFLOW · SYSTEM · HUMAN + AI\n```\n\n---\n\n## Governance Model\n\n**Human-governed.** Every consequential action follows:\n\n```text\nHuman or Twin intent\n      ↓\nContext and evidence assembly\n      ↓\nCapability resolution\n      ↓\nPolicy evaluation\n      ↓\nAllowed / Approval Required / Blocked\n      ↓\nGoverned execution\n      ↓\nResult and verification\n      ↓\nReconciliation\n      ↓\nState, evidence and memory update\n```\n\n---\n\n## Loop State\n\n```text\nIDENTIFIED\n    ↓\nCONTEXTUALIZED\n    ↓\nDEFINED\n    ↓\nALLOCATED\n    ↓\nDECIDING\n    ↓\nEXECUTING\n    ↓\nOBSERVING\n    ↓\nRECONCILING\n    ↓\nLEARNING\n    ↓\nNEXT WORK\n```\n\n---\n\n## How Data Becomes Knowledge\n\n```text\nSOURCE DATA\n      ↓\nINGESTION\n      ↓\nNORMALIZATION\n      ↓\nENTITY RESOLUTION\n      ↓\nCONTEXTUALIZATION\n      ↓\nSPINE\n      ↓\nWORK / DECISION / ACTION\n      ↓\nEXECUTION\n      ↓\nOBSERVED RESULT\n      ↓\nRE-INGESTION\n      ↓\nRECONCILIATION\n      ↓\nEVIDENCE\n      ↓\nPATTERN\n      ↓\nGOVERNED PROMOTION\n      ↓\nORGANIZATIONAL MEMORY\n      ↓\nKNOWLEDGE\n```\n\n**Data does not become organizational knowledge merely because it entered Spine.**\nIt becomes knowledge through **context + experience + outcome + evidence + validation**.\n\n---\n\n## Communication Bridge\n\n```text\n                    BUSINESS CONTEXT SPINE\n                            │\n                            ▼\n                  COMMUNICATION BRIDGE\n                            │\n           ┌────────────────┼────────────────┐\n           │                │                │\n          ADK         ORCHESTRATOR          ACP\n           │                │                │\n           └────────────────┼────────────────┘\n                            │\n                   Agent / Work Context\n                            │\n                 ┌──────────┼──────────┐\n                 │          │          │\n                MCP      Workflow      API\n                 │          │          │\n                 └──────────┼──────────┘\n                            ▼\n                    EXECUTION FABRIC\n```\n\n| Component        | Role                                                      |\n| ---------------- | --------------------------------------------------------- |\n| Business Context Spine | THE organization's memory and semantic foundation    |\n| Bridge           | Controlled communication and context exchange             |\n| ADK              | Agent development and runtime abstraction                 |\n| Orchestrator     | Coordinates context, intelligence, work, and capabilities |\n| ACP              | Agent-to-agent and Twin-to-agent communication            |\n| MCP              | AI-to-tool and AI-to-resource communication               |\n| Execution Fabric | Mechanisms that perform actions in systems                |\n| Governance       | Authority, policy, risk, approval, evidence, and audit    |\n\n---\n\n## Source Systems\n\nSpineWorkspace does **NOT** replace:\n\n- CRM (Salesforce, HubSpot)\n- Documentation (Google Drive, Notion, Coda, Confluence)\n- Communication (Slack, Teams)\n- ERP, billing, finance, support, product systems\n\n```text\nSPINEWORKSPACE\n      │\n      ▼\nGOVERNED ACTION\n      │\n      ▼\nSOURCE SYSTEM\n      │\n      ▼\nACTUAL RESULT\n      │\n      ▼\nRE-INGEST\n```\n\n---\n\n## Reconciliation\n\nExecution success ≠ business success.\n\n```text\nINTENDED ACTION\n      ↓\nEXECUTION\n      ↓\nSOURCE RESULT\n      ↓\nOBSERVED STATE\n      ↓\nRECONCILIATION\n  │\n  ├── Matched\n  ├── Partial\n  ├── Failed\n  ├── Conflicting\n  └── Requires human review\n```\n\nThen:\n\n```text\nRECONCILIATION\n      ↓\nLOOP STATE\n      ↓\nSPINE\n      ↓\nMEMORY\n```\n\n---\n\n## GTM Statements\n\n### One-line company\n\n> **IntegrateWise builds the governed infrastructure that lets humans, AI, workflows, and connected systems work together around shared Business Context.**\n\n### One-line product\n\n> **SpineWorkspace is the Business Context-driven human-AI work environment where people and AI turn connected software into shared context, coordinated work, governed execution, and organizational continuity.**\n\n### Short pitch\n\n> Most organizations have plenty of software and increasingly plenty of AI, but their work is still fragmented. Context sits across CRM, communication, documents, finance, support, product, and project tools; people spend their time assembling the story, coordinating handoffs, and repeating routine work.\n>\n> SpineWorkspace sits above that ecosystem. It creates a shared Business Context and work layer where each person sees what matters for their role, their current work, and their authority. Their AI Twin works alongside them to gather context, prepare work, coordinate routine tasks, and execute approved actions through the existing systems of record.\n>\n> Every result is re-ingested and reconciled, so the organization retains the evidence, outcome, and learning needed for the next decision. Humans govern the business. AI helps the business work. Spine preserves continuity.\n\n### Customer-facing\n\n> **Your software stays. Your work comes together.**\n>\n> SpineWorkspace connects to the systems your business already uses and assembles the right context, tasks, decisions, communications, and actions around the work in front of you. Your AI Twin helps prepare and coordinate work, while you retain control over priorities, commitments, and approvals. Every action is governed, reconciled, and carried forward as Business Context.\n"}