{"slug":"docs/business-context-spine","title":"Business Context Spine — THE Organization's Memory","section":"docs","sectionLabel":"Docs","status":"unclassified","type":"document","path":"docs/business-context-spine.mdx","bytes":3865,"description":"The Business Context Spine IS the organization's memory. It is not merely a database — it is what the system knows.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## What is the Business Context Spine?\n\nThe Business Context Spine is the **tenant-scoped system of organizational operating context, continuity, and governed state**.\n\nIt is not merely a database. It is not an ESB. It is not a data lake.\n\n\n**The Business Context Spine IS the organization's memory.** What the system knows, what is true enough to operate on, what is happening, what was decided, and what happened next.\n\n\n## The Spine Gives Work Its Business Context\n\nWithout the Business Context Spine, Work has no meaning. The Spine connects:\n\n- Organizational goals and objectives\n- Business 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## Spine Architecture\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 vs Operational\n\nThe Spine has two layers:\n\n| Layer | What it is | Who uses it |\n|-------|-----------|-------------|\n| **Canonical Spine** | Governed organizational truth | Humans, governance processes |\n| **Operational Sandbox** | Bounded working context | AI, agents, runtime |\n\n\n**AI does NOT receive unrestricted access to canonical organizational truth.** AI operates on the governed operational sandbox derived from the Business Context Spine.\n\n\n## What the Spine Preserves\n\nThe Spine preserves:\n\n- **Entities** — accounts, deals, tickets, contracts, projects\n- **Relationships** — how entities connect\n- **Events** — what happened and when\n- **Decisions** — what was decided and why\n- **Evidence** — supporting data for claims\n- **Work** — what needs to happen\n- **Outcomes** — what actually happened\n- **Provenance** — where data came from\n- **Continuity** — how context persists across time\n\n## How Data Becomes Business Context\n\n```text\nSOURCE DATA\n      ↓\nINGESTION\n      ↓\nNORMALIZATION\n      ↓\nENTITY RESOLUTION\n      ↓\nCONTEXTUALIZATION\n      ↓\nBUSINESS CONTEXT SPINE\n      ↓\nWORK / DECISION / ACTION\n      ↓\nEXECUTION\n      ↓\nOBSERVED RESULT\n      ↓\nRE-INGESTION\n      ↓\nRECONCILIATION\n      ↓\nEVIDENCE\n      ↓\nGOVERNED PROMOTION\n      ↓\nBUSINESS CONTEXT UPDATED\n```\n\nData does not become Business Context merely because it entered the Spine. It becomes Business Context through **context + experience + outcome + evidence + validation**.\n\n## The Three Memory Domains\n\n| Domain | What it is | Relationship to Spine |\n|--------|------------|----------------------|\n| **Business Context (Spine)** | THE organization's memory | THE thing |\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\nBusiness 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\n## The Invariant\n\n> **Provider schema is not canonical organizational schema.**\n\nThe Spine transforms provider-specific data into canonical organizational context. This transformation is mandatory and non-negotiable.\n"}