01 · Business Context

The organizing center of SpineWorkspace.

Business 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.

BUSINESS CONTEXT
       ↓
      WORK
       ↓
HUMAN + AI
       ↓
   EXECUTION
       ↓
   RECONCILIATION
       ↓
BUSINESS CONTEXT

---

What Business Context Is

Business Context is the complete, living model of what the organization is trying to achieve and what is happening in pursuit of those goals.

                    ORGANIZATION
                         │
            ┌────────────┴────────────┐
            │                         │
        GOALS / NEEDS             BUSINESS EVENTS
            │                         │
            └────────────┬────────────┘
                         ▼
               BUSINESS CONTEXT

It consists of four pillars:

1. Goals

What the organization is trying to achieve.

• Strategic objectives
• Revenue targets
• Customer outcomes
• Operational targets
• Compliance requirements
• Growth milestones

2. Needs

What the organization requires to function and grow.

• Customer needs
• Employee needs
• System needs
• Market needs
• Regulatory needs

3. Entities

The things that constitute the business reality.

• People (employees, customers, partners)
• Accounts (companies, organizations)
• Products and services
• Assets (contracts, documents, data)
• Relationships (who connects to what)

4. Events

What is happening in the business right now.

• Customer interactions
• Financial transactions
• Operational activities
• System events
• Communication signals

---

Why Business Context Is the Center

Without Business Context, every other layer is meaningless:

Layer	Without Business Context
Spine	Has data, no meaning
Workbench	Has tools, no purpose
Twin	Has intelligence, no direction
Agents	Has capability, no intent
Execution	Has action, no reason
Reconciliation	Has verification, no standard

Business Context is what transforms raw data into meaningful work.

---

Business Context Is Not Static

Business Context is not a document that gets written once and forgotten. It is a living, breathing model that:

• Updates continuously as events occur
• Evolves as goals change
• Deepens as patterns emerge
• Corrects as mistakes are discovered
• Learns as outcomes are observed

The Spine Fabric is what maintains Business Context across time.

---

Business Context Is the Input to Everything

Every downstream layer reads from Business Context:

Business Context
      ↓
Spine Fabric (stores and maintains it)
      ↓
Projections (shapes it for roles)
      ↓
Workbench (presents it to humans and twins)
      ↓
Work Allocation (assigns work based on it)
      ↓
Governance (evaluates against it)
      ↓
Execution (acts on it)
      ↓
Reconciliation (verifies against it)
      ↓
Business Context (updated with results)

---

Business Context Is the Output of Everything

Every upstream layer writes back to Business Context:

Source	What It Contributes
Ingestion	New events and data from source systems
Normalization	Resolved entities and relationships
Execution	Actions taken and their outcomes
Reconciliation	Verified state changes
Memory	Learned patterns and decisions
Twin	Reasoning and recommendations
Human	Decisions and approvals

---

The Business Context Contract

interface BusinessContext {
  tenantId: string;
  
  goals: Goal[];
  needs: Need[];
  entities: Entity[];
  events: Event[];
  
  relationships: Relationship[];
  constraints: Constraint[];
  
  lastUpdated: string;
  version: number;
}

---

Business Context Is Shared

Business Context is the same across all roles and domains:

• A Sales Manager and a Finance Analyst see different projections of the same Business Context
• The Twin and the Human work against the same Business Context
• Domain agents reason within the same Business Context
• Governance evaluates against the same Business Context

There is one Business Context per organization. Projections make it role-appropriate.

---

Business Context Connects to

Layer	Relationship
Spine Fabric	Stores and maintains Business Context
Organizational Memory	Accumulates knowledge from Business Context
Work Graph	Derives work from Business Context
Projections	Shapes Business Context for roles
Reconciliation	Verifies Business Context updates
Loop State	Closes back to Business Context