Business Context Spine — THE Organization's Memory
The Business Context Spine IS the organization's memory. It is not merely a database — it is what the system knows.
What is the Business Context Spine?
The Business Context Spine is the tenant-scoped system of organizational operating context, continuity, and governed state.
It is not merely a database. It is not an ESB. It is not a data lake.
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.
The Spine Gives Work Its Business Context
Without the Business Context Spine, Work has no meaning. The Spine connects:
- Organizational goals and objectives
- Business entities and relationships
- Work and work state
- Decisions and evidence
- Events and timelines
- Provenance and lineage
- Operational state
- Validated outcomes
- Governed organizational memory
Spine Architecture
BUSINESS CONTEXT SPINE
├── Business Context (THE semantic foundation)
├── Canonical Spine
├── Operational Spine / Runtime State
├── Linked Business Context
├── Work
├── Entity State
├── Event History
├── Organizational Memory
├── Provenance
├── Lineage
├── Projections
├── Reconciliation
└── Continuity
Canonical vs Operational
The Spine has two layers:
| Layer | What it is | Who uses it |
|---|---|---|
| Canonical Spine | Governed organizational truth | Humans, governance processes |
| Operational Sandbox | Bounded working context | AI, agents, runtime |
AI does NOT receive unrestricted access to canonical organizational truth. AI operates on the governed operational sandbox derived from the Business Context Spine.
What the Spine Preserves
The Spine preserves:
- Entities — accounts, deals, tickets, contracts, projects
- Relationships — how entities connect
- Events — what happened and when
- Decisions — what was decided and why
- Evidence — supporting data for claims
- Work — what needs to happen
- Outcomes — what actually happened
- Provenance — where data came from
- Continuity — how context persists across time
How Data Becomes Business Context
SOURCE DATA
↓
INGESTION
↓
NORMALIZATION
↓
ENTITY RESOLUTION
↓
CONTEXTUALIZATION
↓
BUSINESS CONTEXT SPINE
↓
WORK / DECISION / ACTION
↓
EXECUTION
↓
OBSERVED RESULT
↓
RE-INGESTION
↓
RECONCILIATION
↓
EVIDENCE
↓
GOVERNED PROMOTION
↓
BUSINESS CONTEXT UPDATED
Data does not become Business Context merely because it entered the Spine. It becomes Business Context through context + experience + outcome + evidence + validation.
The Three Memory Domains
| Domain | What it is | Relationship to Spine |
|---|---|---|
| Business Context (Spine) | THE organization's memory | THE thing |
| Personal Contextual Memory | Human's working notes | Working continuity that SERVES Business Context |
| AI Continuity Memory | Twin/agent working state | Working continuity that SERVES Business Context |
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.
The Invariant
Provider schema is not canonical organizational schema.
The Spine transforms provider-specific data into canonical organizational context. This transformation is mandatory and non-negotiable.