{"slug":"product/spine-fabric","title":"Business Context Ingestion & Synthesis","section":"product","sectionLabel":"Product","status":"unclassified","type":"document","path":"product/spine-fabric.mdx","bytes":2623,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n\n\n## Objective\n\nTurn fragmented source data into connected **Business Context** in the Business Context Spine.\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## Pipeline\n\n```text\nSource Systems\n→ Connectivity\n→ Loader\n→ Raw Evidence\n→ Normalization\n→ Schema Synthesis\n→ Entity Resolution\n→ Relationship Linking\n→ Event Linking\n→ Business Context\n→ Business Context Spine\n```\n\n## Source classes\n\n- structured records;\n- unstructured documents;\n- communications;\n- events;\n- AI session outputs;\n- external agent results.\n\n## Stages\n\n### 1. Connect\nAuthenticate and establish scoped provider access.\n\n### 2. Ingest\nCapture source data/events without prematurely changing canonical meaning.\n\n### 3. Normalize\nConvert provider-specific representations to stable normalized primitives.\n\n### 4. Synthesize\nMap provider semantics to canonical Spine concepts.\n\n### 5. Resolve\nResolve identity, duplicates, conflicts and relationships.\n\n### 6. Contextualize\nLink data to organization, domain, entity, Work, user and time.\n\n### 7. Govern\nDetermine whether the result is evidence, state, candidate memory or another category.\n\n### 8. Persist\nWrite to the correct governed layer.\n\n## Core invariant\n\n> Provider schema is not canonical organizational schema.\n\n## Output\n\nThe result is not merely a normalized database. It is connected **Business Context** that can support human projections, Twin context, Work, reconciliation and organizational memory — all stored in the Business Context Spine.\n\n## The Three Memory Domains\n\n| Domain | What it is | Relationship to Business Context |\n|---|---|---|\n| **Business Context (Spine)** | THE organization's memory | **THE thing.** Without it, nothing works. |\n| **Personal Contextual Memory** | Human's working notes | Working continuity that SERVES Business Context. |\n| **AI Continuity Memory** | Twin/agent working state | Working continuity that SERVES Business Context. |\n\n**Business Context is NOT a feature.** It IS the semantic substrate that gives the entire workspace meaning. Personal Contextual Memory and AI Continuity Memory are not equal peers to Business Context. They are working continuities that serve it.\n"}