{"slug":"docs/business-context","title":"Business Context — The Semantic Foundation","section":"docs","sectionLabel":"Docs","status":"unclassified","type":"document","path":"docs/business-context.mdx","bytes":4109,"description":"Business Context is the Tier-0 semantic foundation of SpineWorkspace. Without it, nothing works.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## What is Business Context?\n\nBusiness Context is the **complete, connected representation of organizational reality** required to understand, decide, coordinate, execute, and continue business work.\n\nIt is not a database table. It is not a document. It is not a vector index. It is the **semantic substrate** that gives the entire workspace meaning.\n\n\n**Without Business Context, there is no SpineWorkspace.** 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\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.\n\nThis is not a feature. It IS the system.\n\n```text\nBUSINESS CONTEXT\n      │\n      ▼\n  Everything else\n```\n\n## What Business Context Contains\n\nBusiness Context contains or links to:\n\n| Domain | Examples |\n|--------|----------|\n| **Organization** | Structure, departments, teams, functions |\n| **Goals & Objectives** | Strategic priorities, KPIs, targets |\n| **People & Roles** | Who does what, who decides what |\n| **Business Entities** | Accounts, deals, tickets, contracts, projects |\n| **Relationships** | How entities connect to each other |\n| **Events** | What happened and when |\n| **Current State** | What is true right now |\n| **Historical State** | What was true before |\n| **Decisions** | What was decided and why |\n| **Communications** | Emails, messages, meeting notes |\n| **Evidence** | Supporting data for claims |\n| **Policies** | Rules, guardrails, governance |\n| **Work** | What needs to happen |\n| **Outcomes** | What actually happened |\n\n## The Fundamental Loop\n\nBusiness Context participates in a continuous loop:\n\n```text\nBusiness → Context → Work → Action → Outcome → Context\n```\n\n**Not:**\n\n```text\nApplication → AI → tool call → result\n```\n\nThe second loop is exactly the fragmented model SpineWorkspace replaces.\n\n## Business Context vs Data\n\n| Data | Business Context |\n|------|------------------|\n| Raw records from source systems | Connected, interpreted organizational reality |\n| Provider schema | Canonical organizational schema |\n| Fragmented across silos | Unified in the Business Context Spine |\n| No inherent meaning | Meaning derived from organizational goals |\n| Static snapshots | Continuous, evolving, looped |\n\n## Business Context vs Memory\n\nBusiness Context IS the organization's memory. Personal Contextual Memory and AI Continuity Memory are working continuities that **serve** Business Context — they are not equal peers to it.\n\n| Domain | What it is | Relationship to BC |\n|--------|------------|-------------------|\n| **Business Context** | THE organization's memory | THE thing |\n| **Personal Contextual Memory** | Human's working notes | Serves BC |\n| **AI Continuity Memory** | Twin/agent working state | Serves BC |\n\n## How Business Context is Established\n\nBusiness Context is established through:\n\n1. **Ingestion** — connecting to source systems\n2. **Normalization** — converting provider schemas to canonical primitives\n3. **Entity Resolution** — identifying duplicates, conflicts, relationships\n4. **Contextualization** — linking data to organization, domain, entity, Work, user, time\n5. **Governance** — determining whether results become evidence, state, or candidate memory\n6. **Promotion** — validated outcomes become Business Context through governed approval\n\n## The Feature Test\n\n> **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\nThis test applies to every feature, capability, screen, and integration. If it cannot pass this test, it does not belong.\n"}