{"slug":"architecture/01_BUSINESS_CONTEXT","title":"01 · Business Context","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/01_BUSINESS_CONTEXT.mdx","bytes":5287,"description":"The organizing center of SpineWorkspace — everything flows from and returns to business context","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n**The organizing center of SpineWorkspace.**\n\nBusiness Context is not a feature. It is the reason the system exists. Every other layer in SpineWorkspace exists to understand, maintain, serve, or close the loop back to Business Context.\n\n```text\nBUSINESS CONTEXT\n       ↓\n      WORK\n       ↓\nHUMAN + AI\n       ↓\n   EXECUTION\n       ↓\n   RECONCILIATION\n       ↓\nBUSINESS CONTEXT\n```\n\n---\n\n## What Business Context Is\n\nBusiness Context is the complete, living model of what the organization is trying to achieve and what is happening in pursuit of those goals.\n\n```text\n                    ORGANIZATION\n                         │\n            ┌────────────┴────────────┐\n            │                         │\n        GOALS / NEEDS             BUSINESS EVENTS\n            │                         │\n            └────────────┬────────────┘\n                         ▼\n               BUSINESS CONTEXT\n```\n\nIt consists of four pillars:\n\n### 1. Goals\n\nWhat the organization is trying to achieve.\n\n- Strategic objectives\n- Revenue targets\n- Customer outcomes\n- Operational targets\n- Compliance requirements\n- Growth milestones\n\n### 2. Needs\n\nWhat the organization requires to function and grow.\n\n- Customer needs\n- Employee needs\n- System needs\n- Market needs\n- Regulatory needs\n\n### 3. Entities\n\nThe things that constitute the business reality.\n\n- People (employees, customers, partners)\n- Accounts (companies, organizations)\n- Products and services\n- Assets (contracts, documents, data)\n- Relationships (who connects to what)\n\n### 4. Events\n\nWhat is happening in the business right now.\n\n- Customer interactions\n- Financial transactions\n- Operational activities\n- System events\n- Communication signals\n\n---\n\n## Why Business Context Is the Center\n\nWithout Business Context, every other layer is meaningless:\n\n| Layer | Without Business Context |\n|-------|------------------------|\n| Spine | Has data, no meaning |\n| Workbench | Has tools, no purpose |\n| Twin | Has intelligence, no direction |\n| Agents | Has capability, no intent |\n| Execution | Has action, no reason |\n| Reconciliation | Has verification, no standard |\n\nBusiness Context is what transforms raw data into meaningful work.\n\n---\n\n## Business Context Is Not Static\n\nBusiness Context is not a document that gets written once and forgotten. It is a living, breathing model that:\n\n- **Updates continuously** as events occur\n- **Evolves** as goals change\n- **Deepens** as patterns emerge\n- **Corrects** as mistakes are discovered\n- **Learns** as outcomes are observed\n\nThe Spine Fabric is what maintains Business Context across time.\n\n---\n\n## Business Context Is the Input to Everything\n\nEvery downstream layer reads from Business Context:\n\n```text\nBusiness Context\n      ↓\nSpine Fabric (stores and maintains it)\n      ↓\nProjections (shapes it for roles)\n      ↓\nWorkbench (presents it to humans and twins)\n      ↓\nWork Allocation (assigns work based on it)\n      ↓\nGovernance (evaluates against it)\n      ↓\nExecution (acts on it)\n      ↓\nReconciliation (verifies against it)\n      ↓\nBusiness Context (updated with results)\n```\n\n---\n\n## Business Context Is the Output of Everything\n\nEvery upstream layer writes back to Business Context:\n\n| Source | What It Contributes |\n|--------|-------------------|\n| Ingestion | New events and data from source systems |\n| Normalization | Resolved entities and relationships |\n| Execution | Actions taken and their outcomes |\n| Reconciliation | Verified state changes |\n| Memory | Learned patterns and decisions |\n| Twin | Reasoning and recommendations |\n| Human | Decisions and approvals |\n\n---\n\n## The Business Context Contract\n\n```typescript\ninterface BusinessContext {\n  tenantId: string;\n  \n  goals: Goal[];\n  needs: Need[];\n  entities: Entity[];\n  events: Event[];\n  \n  relationships: Relationship[];\n  constraints: Constraint[];\n  \n  lastUpdated: string;\n  version: number;\n}\n```\n\n---\n\n## Business Context Is Shared\n\nBusiness Context is the same across all roles and domains:\n\n- A Sales Manager and a Finance Analyst see different **projections** of the same Business Context\n- The Twin and the Human work against the same Business Context\n- Domain agents reason within the same Business Context\n- Governance evaluates against the same Business Context\n\nThere is one Business Context per organization. Projections make it role-appropriate.\n\n---\n\n## Business Context Connects to\n\n| Layer | Relationship |\n|-------|-------------|\n| [Spine Fabric](/architecture/02_SPINE_FABRIC) | Stores and maintains Business Context |\n| [Organizational Memory](/architecture/03_ORGANIZATIONAL_MEMORY) | Accumulates knowledge from Business Context |\n| [Work Graph](/architecture/04_WORK_GRAPH) | Derives work from Business Context |\n| [Projections](/architecture/05_PROJECTIONS) | Shapes Business Context for roles |\n| [Reconciliation](/architecture/15_RECONCILIATION) | Verifies Business Context updates |\n| [Loop State](/architecture/16_LOOP_STATE) | Closes back to Business Context |\n"}