{"slug":"architecture/PRODUCT_FRAMING_LOCK","title":"IntegrateWise / SpineWorkspace — Product Framing Lock","section":"architecture","sectionLabel":"Architecture","status":"superseded","type":"document","path":"architecture/PRODUCT_FRAMING_LOCK.md","bytes":11029,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** SUPERSEDED BY FOUNDER CANON  \n**Effective:** 2026-08-25  \n**Superseded by:** `docs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` (31 August 2026)  \n**Scope:** Product identity, business model, system narrative and terminology  \n**Authority:** This document is retained as historical reference. The Founder Canon is now the authoritative source for product framing and terminology.\n\n> **This document is superseded.** The 31 August 2026 Founder Canon (`docs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md`) is the authoritative source for product framing, terminology and architecture. This file is retained for migration reference only.\n\n---\n\n## 1. Company and product\n\n| Term | Canonical meaning |\n|---|---|\n| **IntegrateWise** | The company and platform builder. |\n| **integratewise.ai** | IntegrateWise company/platform domain. |\n| **SpineWorkspace** | The customer product and work environment built by IntegrateWise. |\n| **spineworkspace.com** | SpineWorkspace product domain. |\n\nNever use IntegrateWise as the product name. Never use SpineWorkspace as the company name.\n\n## 2. Core product thesis\n\n> **SpineWorkspace is the shared operational work environment where humans and AI work together toward business objectives using contextual business memory, governed work allocation and connected execution across the software a business already uses.**\n\nThe central problem is not simply automation. Business work is fragmented across people, systems, communication channels, data stores and AI systems. SpineWorkspace coordinates that work while preserving context, authority, accountability and continuity.\n\n## 3. Core value chain\n\n```text\nBusiness Goals / Needs\n        ↓\nFragmented Business Work\n        ↓\nConnected Systems\n        ↓\nBusiness Context Ingestion & Synthesis\n        ↓\nSpine Fabric\n        ↓\nRole / Domain / Responsibility Projection\n        ↓\nHuman Workbench + Twin Workbench\n        ↓\nHuman + Twin + Agents\n        ↓\nGoverned Execution\n        ↓\nSource Systems\n        ↓\nRe-ingestion\n        ↓\nVerification / Reconciliation\n        ↓\nGoverned Organizational Memory\n        ↓\nBetter Context for Next Work\n```\n\n## 4. Spine Fabric\n\nSpine is the contextual business-memory and operational-continuity substrate of SpineWorkspace.\n\nIt connects and preserves:\n\n- organizational context;\n- entities and relationships;\n- work and work state;\n- decisions and evidence;\n- events and timelines;\n- provenance and lineage;\n- operational state;\n- validated outcomes;\n- governed organizational memory.\n\n### Canonical Spine vs operational sandbox\n\nThe distinction is mandatory:\n\n```text\n                 SPINE FABRIC\n                       │\n           ┌───────────┴───────────┐\n           │                       │\n    CANONICAL SPINE          OPERATIONAL SANDBOX\n    governed truth           bounded working context\n           │                       │\n    organizational         Human/AI operational work\n    memory + continuity    with governed context\n```\n\nAI does **not** receive unrestricted direct access to canonical organizational truth. AI operates on the governed operational context/sandbox derived from Spine.\n\n## 5. Business Context Ingestion & Synthesis\n\nThe first system flow is:\n\n```text\nSource Tools\n   ↓\nConnector / Ingestion\n   ↓\nPreprocessor\n   ↓\nNormalization / Identity Resolution\n   ↓\nTriage\n   ↓\nContext Assembly\n   ↓\nSpine Fabric\n```\n\nTriage classifies and routes information. It does not independently promote information into canonical organizational memory.\n\nThe governing principle is:\n\n> **Triage classifies. Governance decides. Pipeline promotes. Spine owns organizational memory. Twin consumes governed context.**\n\n## 6. Projection model\n\nThe organization has one underlying business reality. Users do not receive separate copies of that reality.\n\n```text\nOrganization / Business Context\n              ↓\n         Spine Schema\n              ↓\n      Projection Engine\n              ↓\n   Role + Domain + Responsibility\n   + Authority + Relevance + Policy\n              ↓\n        User Projection\n```\n\nThe same organizational context can therefore appear differently to Sales, Finance, Operations, Engineering, HR, executives and other roles without duplicating canonical truth.\n\n## 7. Human Workbench\n\nThe Human Workbench is the human operational surface of SpineWorkspace.\n\nIt projects the user's relevant business context and work rather than recreating every connected SaaS application.\n\nCanonical experience areas include:\n\n- **Today / Personal Work** — what needs attention now;\n- **Communications** — relevant team and business communication;\n- **Organization Memory / Knowledge** — organizational documents, decisions, calls and retained context;\n- **Work** — the user's business work, entities, operational views and domain/KPI context.\n\nThe Workbench is adaptive through projections, not through separate products or separate truth stores.\n\n## 8. Twin Workbench\n\nEach user receives one **Twin** for their work.\n\nThe Twin is the user's AI work partner and coordination intelligence. It operates on governed operational context and can:\n\n- understand the current work;\n- assemble relevant context;\n- reason and propose;\n- coordinate work;\n- delegate bounded work to agents;\n- invoke governed capabilities;\n- monitor execution;\n- verify results;\n- report outcomes;\n- adapt future work from validated outcomes.\n\nThe Twin is not a second organizational authority and does not become the owner of canonical truth.\n\n## 9. Coworker\n\n**Coworker** is the contextual companion between active Human Workbench interaction and the Twin.\n\nIt gathers context from the user's active interaction, retrieves relevant information, assists communication and helps maintain continuity between what the user is doing and what the Twin needs to know.\n\nCoworker is **not** a second orchestration authority.\n\n## 10. Shared work allocation\n\nWork is the primary coordination unit. Tasks are components of Work.\n\nFor each part of Work, SpineWorkspace can determine whether it should be performed by:\n\n- Human;\n- Twin;\n- Domain/specialist agent;\n- External agent;\n- Connected system/workflow;\n- Human + AI together.\n\nAllocation considers capability, authority, responsibility, risk, complexity, context, urgency, cost, availability and policy.\n\n## 11. Communication over the Bridge\n\nThe Bridge is the governed communication and execution boundary around Spine.\n\n```text\nHuman Workbench\n      ↕\n     Spine\n      ↕\n     Twin\n      ↕\n   Agents / Workflows\n      ↕\nMCP / ACP / ADK / Orchestrator\n      ↕\nConnected Tools / Services\n```\n\n- **MCP:** AI ↔ tool/resource interaction.\n- **ACP:** governed agent ↔ agent/Twin contextual handoff.\n- **ADK:** agent development/runtime mechanism.\n- **Orchestrator:** coordinates durable execution, dependencies, retries, approvals and bounded agent work.\n\nThese are mechanisms of the platform. They are not the product's primary abstraction.\n\n## 12. Execution and continuity loop\n\nExecution is not complete merely because a tool returned success.\n\n```text\nNeed\n ↓\nGoal\n ↓\nWork Graph\n ↓\nContext\n ↓\nProjection\n ↓\nHuman / Twin\n ↓\nAllocation\n ↓\nGovernance\n ↓\nExecution\n ↓\nSource System State\n ↓\nRe-ingestion\n ↓\nVerification\n ↓\nReconciliation\n ↓\nMemory / Knowledge Promotion\n ↓\nNext Work\n```\n\nThe loop state must remain observable throughout the lifecycle.\n\n## 13. How information becomes organizational knowledge\n\nProcessed source information becomes useful organizational knowledge through a governed lifecycle:\n\n```text\nSource Data\n  → Context\n  → Work\n  → Decision\n  → Action\n  → Outcome\n  → Re-ingestion\n  → Verification\n  → Reconciliation\n  → Governance\n  → Memory Promotion\n  → Organizational Knowledge\n```\n\nMemory is therefore not merely imported data. It is validated, contextualized and governed organizational knowledge that can improve future work.\n\n## 14. Platform substrate\n\nIntegrateWise provides the substrate required to run each unit of operational work, including:\n\n- identity and tenant boundary;\n- connected-system authority and discovery;\n- connectivity and connector projections;\n- contextual business memory and Spine infrastructure;\n- AI and agent runtime;\n- execution and orchestration;\n- communication bridge;\n- governance and policy enforcement;\n- MCP/ACP/ADK integration;\n- pipelines, synchronization and reconciliation;\n- observability and infrastructure.\n\nThe commercial/product model can therefore be expressed as:\n\n> **IntegrateWise provides the infrastructure substrate; SpineWorkspace provides the business work environment.**\n\n## 15. Canonical terminology\n\n| Term | Definition |\n|---|---|\n| Business Context | Connected representation of the organization's relevant business reality. |\n| Spine Fabric | Contextual business-memory and operational-continuity substrate. |\n| Canonical Spine | Governed organizational truth. |\n| Operational Sandbox | Bounded working representation exposed to AI/runtime participants. |\n| Work | Primary unit of coordinated business activity. |\n| Work Graph | Connected representation of objectives, work, entities, people, agents, actions, decisions and outcomes. |\n| Projection | Role/domain/responsibility/authority-specific view of shared business context. |\n| Human Workbench | Human-facing operational work surface. |\n| Twin Workbench | Agentic work environment used by the user's Twin. |\n| Twin | User-specific AI work partner and work coordinator. |\n| Coworker | Contextual companion for active Workbench interaction and communication. |\n| Work Allocation | Decision about who/what should perform each part of Work. |\n| Capability | Governed statement of what can be done. |\n| Execution Fabric | Mechanisms that perform authorized work. |\n| Governance | Authority, policy, risk, approval, evidence and accountability controls. |\n| Bridge | Governed communication and execution boundary. |\n| Reconciliation | Verification that intended work produced the expected external/business state. |\n| Continuity | Preservation of relevant context, state, decisions and progress across time, systems, people and AI. |\n\n## 16. Relationship to the technical architecture lock\n\nThis document locks **product framing and terminology**. It does not silently amend implementation contracts.\n\nWhere an implementation contract is frozen elsewhere, engineering must preserve that contract until the contract itself is explicitly changed and versioned.\n\nThe product framing target is therefore:\n\n```text\nINTEGRATEWISE\nCompany / platform builder\n        ↓\nSPINEWORKSPACE\nCustomer product\n        ↓\nBUSINESS CONTEXT\n        ↓\nSPINE FABRIC\n        ↓\nPROJECTIONS\n        ↓\nHUMAN WORKBENCH + TWIN WORKBENCH\n        ↓\nBRIDGE / EXECUTION\n        ↓\nSOURCE SYSTEMS\n        ↓\nRE-INGESTION / RECONCILIATION\n        ↓\nORGANIZATIONAL MEMORY\n        ↓\nNEXT WORK\n```\n"}