{"slug":"public/product/what-is-spineworkspace","title":"SpineWorkspace — Full Canonical Ontology & End-to-End Work Model","section":"public","sectionLabel":"Public","status":"unclassified","type":"document","path":"public/product/what-is-spineworkspace.md","bytes":17363,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: PUBLIC | SOURCE: 01_SPINEWORKSPACE_FULL_ONTOLOGY_AND_FLOWS.md -->\n<!-- STATUS: Aligned with Founder Canon (31 August 2026) -->\n\n# SpineWorkspace — Full Canonical Ontology & End-to-End Work Model\n\n**Status:** CANONICAL TARGET  \n**Company:** IntegrateWise (`integratewise.ai`)  \n**Product:** SpineWorkspace (`spineworkspace.com`)  \n**Foundation:** Business Context Spine (THE semantic foundation)  \n**Primary concern:** Business Context  \n**Primary coordination unit:** Work  \n**Primary human–AI relationship:** User ↔ Twin  \n\n## 0. The ontology in one sentence\n\n> **SpineWorkspace is a human–AI work coordination environment centered on Business Context, with the Business Context Spine providing THE organization's memory, the User Workbench providing the human operating surface, the AI Workbench providing the machine-side operating surface, and the IntegrateWise platform providing governed connectivity, communication, capability and execution.**\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## 1. Root hierarchy\n\n```text\nINTEGRATEWISE\nCompany / Platform Builder\nintegratewise.ai\n│\n└── SPINEWORKSPACE\n    Customer Product\n    spineworkspace.com\n    │\n    ├── ORGANIZATION\n    ├── BUSINESS CONTEXT\n    ├── HOST AWARENESS\n    ├── DISCOVERY / MARKETPLACES\n    ├── CONNECTIVITY / INGESTION\n    ├── CONTEXT INGESTION & SYNTHESIS\n    ├── BUSINESS CONTEXT SPINE\n    ├── PROJECTION\n    ├── WORK\n    ├── HUMAN WORKBENCH\n    ├── AI WORKBENCH\n    ├── TRIAGE\n    ├── AGENT FABRIC\n    ├── AGENT COMMUNICATION\n    ├── CAPABILITY FABRIC\n    ├── GOVERNANCE\n    ├── EXECUTION FABRIC\n    ├── COMMUNICATIONS OVER THE BRIDGE\n    ├── RECONCILIATION\n    ├── MEMORY / KNOWLEDGE\n    └── CONTINUITY\n```\n\n## 2. Dual-domain rule\n\nThe term **dual domain** means the two primary product/company domains:\n\n```text\nintegratewise.ai\n    ↓\nIntegrateWise — company / platform\n\nspineworkspace.com\n    ↓\nSpineWorkspace — product / customer work environment\n```\n\nBusiness domains such as Sales, Finance and Account Success are inside SpineWorkspace. They are not the second half of the dual-domain model.\n\n## 3. Business Context is the center\n\nBusiness Context is:\n\n> **The relevant representation of organizational reality required to understand, decide, coordinate, execute and continue business work.**\n\nIt contains or links:\n\n```text\nBusiness Context\n├── Organization\n├── Goals\n├── Objectives\n├── People\n├── Teams\n├── Roles\n├── Responsibilities\n├── Domains\n├── Business Entities\n├── Relationships\n├── Events\n├── Current State\n├── Historical State\n├── Decisions\n├── Communications\n├── Evidence\n├── Policies\n├── Commitments\n├── Dependencies\n├── Risks\n├── Work\n└── Outcomes\n```\n\nBusiness Context Spine exists to make this context continuous across the organization's existing systems.\n\n## 4. Three canonical flows\n\n### Flow 1 — Business Context Ingestion & Synthesis\n\n```text\nSOURCE SYSTEMS / TOOLS / AGENTS\n        ↓\nCONNECTIVITY\n        ↓\nLOADER\n        ↓\nRAW EVIDENCE\n        ↓\nNORMALIZER\n        ↓\nSCHEMA / SEMANTIC SYNTHESIS\n        ↓\nENTITY RESOLUTION\n        ↓\nRELATIONSHIP / EVENT LINKING\n        ↓\nDOMAIN / ACCOUNT / WORK LINKING\n        ↓\nBUSINESS CONTEXT\n        ↓\nBUSINESS CONTEXT SPINE\n```\n\nThe result is **connected Business Context**, not a collection of copied provider records.\n\n### Flow 2 — Human–AI Work\n\n```text\nBUSINESS CONTEXT SPINE\n        ↓\nPROJECTION\n        ↓\nHUMAN WORKBENCH\n        ↓\nUSER INTERACTION\n        ↓\nBUSINESS CONTEXT ASSEMBLY\n        ↓\nTWIN OBSERVE / ORIENT\n        ↓\nCONTEXT ASSEMBLY\n        ↓\nAI WORKBENCH\n        ↓\nTWIN\n        ↓\nUSER + TWIN + SHARED WORK\n        ↓\nWORK ALLOCATION\n        ↓\nHUMAN / TWIN / AGENT / SYSTEM / HUMAN+AI\n        ↓\nDECIDE\n        ↓\nGOVERNANCE\n        ↓\nEXECUTION\n```\n\n### Flow 3 — Communication, Execution, Reconciliation & Knowledge Continuity\n\n```text\nHUMAN / TWIN / AGENT\n        ↓\nCOMMUNICATIONS OVER THE BRIDGE\n        ↓\nGOVERNED CONTEXT SHARING\n        ↓\nCAPABILITY\n        ↓\nGOVERNANCE\n        ↓\nEXECUTION FABRIC\n        ↓\nSOURCE SYSTEM\n        ↓\nACTUAL STATE\n        ↓\nRE-INGESTION\n        ↓\nNORMALIZATION\n        ↓\nRECONCILIATION\n        ↓\nUPDATED BUSINESS CONTEXT\n        ↓\nTRIAGE / INTERPRETATION\n        ↓\nCANDIDATE\n        ↓\nGOVERNANCE\n        ↓\nORGANIZATIONAL MEMORY\n        ↓\nUPDATED SPINE CONTEXT\n        ↓\nNEXT WORK\n```\n\n## 5. Source-to-Spine ontology\n\n### Loader\n\nThe Loader preserves:\n\n- source identity\n- tenant identity\n- provenance\n- evidence\n- ingestion metadata\n- replay information\n\nIt does not decide canonical meaning.\n\n### Normalizer\n\nThe Normalizer makes source structures structurally comparable:\n\n- fields\n- types\n- timestamps\n- identifiers\n- enums\n- events\n- source mappings\n\n### Schema Synthesis\n\nSchema Synthesis turns provider structures into canonical organizational semantics.\n\n```text\nprovider schema\n    ↓\nnormalized schema\n    ↓\nsemantic synthesis\n    ↓\ncanonical entity / relationship / event\n```\n\n### Entity Resolution\n\nEntity Resolution answers:\n\n> Are two provider records the same business entity?\n\n```text\nSalesforce Account\nStripe Customer\nHubSpot Company\n        ↓\n    canonical Account\n```\n\n### Relationship Linking\n\nRelationships connect otherwise isolated records into Business Context.\n\n### Event Linking\n\nEvents become temporally connected to:\n\n- entities\n- work\n- decisions\n- communications\n- outcomes\n\n### Domain Mapping\n\nOne business event may appear in multiple domain projections without creating multiple truths.\n\n## 6. Business Context Spine\n\n```text\nBUSINESS CONTEXT SPINE\n├── Business Context (THE semantic foundation)\n├── Canonical Spine\n├── Operational Spine / Runtime State\n├── Linked Business Context\n├── Work\n├── Entity State\n├── Event History\n├── Organizational Memory\n├── Provenance\n├── Lineage\n├── Projections\n├── Reconciliation\n└── Continuity\n```\n\n### Canonical Spine\n\nGoverned organizational truth.\n\n### Operational Sandbox\n\nBounded working context derived from Business Context Spine for a user, role, task and interaction.\n\nAI works in the sandbox.\n\nAI does not directly own or mutate canonical Business Context Spine.\n\n## 7. Organization ontology\n\n```text\nOrganization\n├── Identity\n├── Structure\n│   ├── Business Units\n│   ├── Departments\n│   ├── Teams\n│   └── Functions\n├── People\n├── Roles\n├── Responsibilities\n├── Authority\n├── Business Domains\n├── Goals\n├── Objectives\n├── Standards\n├── Policies\n├── Processes\n├── Capabilities\n└── Outcomes\n```\n\nOrganizational lifecycle:\n\n```text\nNEED\n ↓\nGOAL\n ↓\nOBJECTIVE\n ↓\nPLAN\n ↓\nWORK\n ↓\nASSIGN\n ↓\nEXECUTE\n ↓\nMONITOR\n ↓\nDECIDE\n ↓\nVERIFY\n ↓\nRECONCILE\n ↓\nOUTCOME\n ↓\nLEARN\n ↓\nNEXT WORK\n```\n\n## 8. Business domain taxonomy\n\n```text\nExecutive / Corporate\nSales\nMarketing\nAccount Success\nTechnical Account Success\nSupport / Service\nFinance\nRevenue Operations\nBusiness Operations\nProduct\nEngineering\nHuman Resources\nLegal\nIT\nSecurity / Risk\nProcurement\nAdministration\n```\n\nSubdomains remain organization-configurable.\n\n## 9. Entity ontology\n\n```text\nOrganization\nPerson\nTeam\nRole\nCustomer\nAccount\nContact\nProduct\nContract\nOpportunity\nDeal\nInvoice\nPayment\nTicket\nCase\nProject\nDocument\nMeeting\nDecision\nPolicy\nWork\nTask\nWorkflow\nAgent\nCapability\nSystem\nOutcome\n```\n\n## 10. Work Graph ontology\n\nThe Work Graph connects:\n\n```text\nGoal\nObjective\nWork\n ├── Task\n ├── Assignment\n ├── Entity\n ├── Dependency\n ├── Decision\n ├── Approval\n ├── Communication\n ├── Evidence\n ├── Capability\n ├── Agent\n ├── Execution\n └── Outcome\n```\n\nA task is a component of Work. Work may span people, domains, systems, communications and agents while remaining one continuity thread.\n\n## 11. Projection ontology\n\nProjection is a governed view over the same organizational reality.\n\n```text\nViewer\n├── Identity\n├── Tenant\n├── Role\n├── Permissions\n├── Department\n├── Domain\n└── Responsibility\n\nSubject\n├── Entity\n├── Work\n├── Lifecycle\n├── Relationships\n└── Evidence\n\nOrganization\n├── Goals\n├── Priorities\n├── Standards\n└── Business Context\n\nSystem\n├── Connector Availability\n├── Capability Availability\n├── Freshness\n└── Policy\n        ↓\nProjection Engine\n        ↓\nRole / Domain / Responsibility Projection\n```\n\nThere are no departmental copies of canonical truth.\n\n## 12. User Workbench\n\nThe User Workbench is the human operational surface.\n\n```text\nUser Workbench\n├── Personal\n│   ├── Home\n│   ├── Today\n│   ├── My Work\n│   ├── My Queue\n│   ├── Tasks\n│   └── Calendar\n├── Communications\n│   ├── Email\n│   ├── Chat\n│   ├── Meetings\n│   ├── Calls\n│   └── Documents\n├── Organizational Memory\n│   ├── Decisions\n│   ├── Knowledge\n│   ├── Documents\n│   ├── Policies\n│   ├── Processes\n│   └── Work History\n├── Work\n│   ├── Active\n│   ├── Waiting\n│   ├── Needs Decision\n│   ├── Needs Approval\n│   ├── Delegated\n│   ├── Blocked\n│   └── Completed\n└── Business Domain Work Surfaces\n```\n\nThe Workbench is adaptive, but only personal/reversible presentation changes may occur automatically. Shared truth, permissions, authority, policy and organizational-memory publication remain governed.\n\n## 13. Twin ontology\n\nEvery user has one bounded Twin.\n\n```text\nUSER\n├── User Workbench\n└── Twin\n    ├── Twin Workbench\n    ├── AI Operational Sandbox\n    ├── Domain Capabilities\n    ├── Domain Agents\n    ├── Workflows\n    ├── Communications\n    └── Work Assignment\n```\n\nTwin responsibility:\n\n```text\nUNDERSTAND\n ↓\nCONTEXTUALIZE\n ↓\nTRIAGE\n ↓\nALLOCATE\n ↓\nPLAN / PROPOSE\n ↓\nDELEGATE\n ↓\nEXECUTE THROUGH GOVERNED CAPABILITIES\n ↓\nVERIFY\n ↓\nREPORT\n ↓\nADAPT\n```\n\nOODA is the internal reasoning loop:\n\n```text\nOBSERVE → ORIENT → DECIDE → ACT\n```\n\n## 14. Coworker ontology\n\nCoworker is the contextual companion between active Workbench use and the Twin.\n\n```text\nUser\n ↓\nWorkbench\n ↓\nCoworker\n ├── observes active work\n ├── gathers context\n ├── retrieves relevant information\n ├── supports communication\n └── keeps active human/Twin context aligned\n ↓\nTwin\n```\n\nCoworker is not a second authority.\n\n## 15. Triage ontology\n\nTriage:\n\n- classifies\n- links\n- detects duplicates\n- detects conflicts\n- detects ambiguity\n- evaluates materiality\n- evaluates sensitivity\n- evaluates freshness\n- evaluates completeness\n- proposes memory scope\n- stages candidates\n- routes review\n\nCanonical doctrine:\n\n> **Triage classifies. Governance decides. The Pipeline promotes. Spine owns organizational memory. Twin consumes the governed result.**\n\n## 16. Agent Fabric\n\n```text\nAgent Fabric\n├── Twin\n├── Coworker\n├── Triage\n├── Domain Agents\n├── Specialist Agents\n├── Research Agents\n├── Workflow Agents\n└── External Agents\n```\n\nThe Twin remains the orchestration boundary.\n\n## 17. Agent Communication\n\n### ACP\n\nACP is the Agent Communication Protocol.\n\n```text\nMCP = AI ↔ Tool / Resource\nACP = Agent ↔ Agent / Agent ↔ Twin through governed work/context handoff\n```\n\nACP carries:\n\n```text\nWork ID\nTask ID\nSender\nRecipient\nCapability\nContext Reference\nAuthority Scope\nConstraints\nExpected Output\nEvidence Requirements\nStatus\nResult\nAttribution\nCorrelation ID\nCausation ID\n```\n\nACP is a communication mechanism, not an authority grant.\n\n## 18. Context sharing\n\nAgents receive a bounded Context Package:\n\n```text\nTenant\nWork\nPurpose\nRelevant Entities\nRelevant State\nConstraints\nAuthority\nAllowed Capabilities\nEvidence\nFreshness\nSensitivity\nExpiry\nProvenance\n```\n\nThey do not receive unrestricted organizational memory.\n\n## 19. Capability Fabric\n\nCapability answers:\n\n> What can be done?\n\nA capability declares:\n\n```text\nIdentity\nDescription\nInputs\nOutputs\nRequired Context\nRequired Authority\nRisk\nEvidence Requirements\nPolicy\nExecution Bindings\n```\n\nCapability is independent from implementation.\n\n## 20. Execution Fabric\n\n```text\nAPI\nMCP\nSpine Tools\nADK\nWorkflow\nPipeline\nAgent Runtime\nOrchestrator / Hermes\nProvider Tools\nWorkers\nDurable Execution\n```\n\nAll consequential external effects traverse governed Execution Fabric.\n\n## 21. Governance\n\n```text\nIdentity\nTenant\nRole\nPermission\nResponsibility\nAuthority\nPolicy\nRisk\nApproval\nEvidence\nAudit\nAccountability\n```\n\nConfidence never grants authority.\n\n## 22. Communications Over the Bridge\n\nThe Bridge is the communication substrate connecting human, Twin, agents and source systems around the same Work.\n\n```text\nHuman\n │\n ├── Workbench Chat\n ├── Slack\n ├── Email\n ├── Teams\n ├── Meeting\n └── Call\n │\n ▼\nCOMMUNICATION BRIDGE\n │\n ├── Identity / Tenant\n ├── Work Context\n ├── Context Reference\n ├── Policy\n ├── Delivery\n ├── Inbound Event\n └── Audit\n │\n ▼\nTwin / Coworker / Agent / Workflow\n │\n ▼\nSpine Work / Context\n```\n\nThe Bridge does not become a new memory store.\n\nIt transports communication and work context while preserving source provenance.\n\n## 23. Source-system execution and return path\n\n```text\nIntent\n ↓\nCapability\n ↓\nGovernance\n ↓\nExecution Plan\n ↓\nExecution Fabric\n ↓\nSource System\n ↓\nReceipt\n ↓\nActual State\n ↓\nRe-ingestion\n ↓\nReconciliation\n ↓\nSpine\n```\n\nProvider success is not business completion.\n\n## 24. Knowledge evolution\n\n```text\nActual State\n ↓\nEvent\n ↓\nEvidence\n ↓\nContext\n ↓\nInterpretation\n ↓\nTriage\n ↓\nCandidate\n ↓\nGovernance\n ↓\nOrganizational Memory\n ↓\nUpdated Spine\n ↓\nFuture Context\n```\n\nKnowledge therefore emerges from processed outcomes, not from raw data or raw model output.\n\n## 25. Canonical laws\n\n1. IntegrateWise is the company; SpineWorkspace is the product.\n2. **Business Context is THE semantic foundation.** Without it, nothing works.\n3. **The Spine gives work its business context.**\n4. One canonical organizational reality; many governed projections.\n5. AI never directly reads or writes canonical Business Context Spine.\n6. AI operates in a bounded AI Workbench.\n7. Work is the primary coordination unit.\n8. Work Allocation determines who/what performs each part of Work.\n9. Every user has one bounded Twin.\n10. Triage never becomes a canonical writer.\n11. Capability defines what; Execution Fabric defines how.\n12. Governance controls consequential mutation.\n13. ACP communicates work/context; it does not grant authority.\n14. MCP is a tool/resource/capability interoperability mechanism.\n15. Source execution must return through re-ingestion and reconciliation.\n16. Business Context informs organizational truth; it does not silently become organizational truth.\n17. Business Context is published only through governed promotion.\n18. Personal/reversible adaptation may auto-tune; shared/consequential change requires governance.\n19. IntegrateWise Platform remains substrate, not a second Workbench.\n20. If a feature cannot explain how it relates to Business Context, Work, or a Business Outcome, it does not yet have a meaningful place in SpineWorkspace.\n\n## 26. Canonical system loop\n\n```text\nORGANIZATIONAL NEED\n ↓\nGOAL / OBJECTIVE\n ↓\nWORK GRAPH\n ↓\nBUSINESS CONTEXT\n ↓\nBUSINESS CONTEXT SPINE\n ↓\nPROJECTION / CONTEXT ASSEMBLY\n ↓\nHUMAN WORKBENCH + AI WORKBENCH\n ↓\nSHARED WORK\n ↓\nWORK ALLOCATION\n ↓\nHUMAN / AI / HUMAN+AI\n ↓\nCOMMUNICATION / CONTEXT SHARING\n ↓\nGOVERNANCE\n ↓\nCAPABILITY\n ↓\nEXECUTION\n ↓\nSOURCE SYSTEM\n ↓\nRE-INGESTION\n ↓\nRECONCILIATION\n ↓\nUPDATED CONTEXT\n ↓\nTRIAGE / INTERPRETATION\n ↓\nGOVERNED KNOWLEDGE PROMOTION\n ↓\nORGANIZATIONAL MEMORY\n ↓\nCONTINUITY\n ↓\nNEXT WORK\n```\n\n\n## 27. Host-aware and marketplace ontology\n\nHost and marketplace capabilities sit above Connectivity and Capability discovery:\n\n```text\nHOST\n ↓\nDISCOVERY\n ↓\nINTEGRATION MARKETPLACE\nPLUGIN MARKETPLACE\nMCP MARKETPLACE\n ↓\nCOMPATIBILITY / TRUST\n ↓\nINSTALL / CONNECT / AUTHORIZE\n ↓\nCAPABILITY REGISTRY\n ↓\nGOVERNANCE\n ↓\nEXECUTION\n```\n\nHost awareness changes the contextual surface available to the user/Twin. It never creates authority and never changes canonical Business Context.\n\nThe marketplace is not a new source of Business Context. It discovers and distributes capabilities that may participate in Work.\n"}