02 — Business Context Spine Fabric
Canonical reference: 00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md §5
Status: Canonical
Tier-0: This document defines the semantic foundation of SpineWorkspace.
1. Definition
The Business Contextual Spine Fabric is the tenant-scoped system of organizational operating context, continuity and governed state. It is not merely a database and it is not an ESB.
The Business Context Spine IS the organization's memory. It is what the system knows, what is true enough to operate on, what is happening, what was decided, and what happened next. It is the ONE thing that everything else revolves around.
Without Business Context, there is no SpineWorkspace. Business Context is the thread that connects every feature, every surface, every action in the product. The Human Workbench exists to present it. The AI Workbench exists to reason over it. Twin exists to help the human work with it. Spine Agents exist to act on it. Governance protects it. Execution acts on it. Reconciliation verifies it. Memory preserves it. None of it works without Business Context.
The Spine gives work its business context.
The closest ESB analogy is that it provides a common coordination substrate across many systems. The analogy stops there. A traditional integration bus primarily transports, routes and transforms messages. The Spine Fabric preserves the semantic and temporal context needed for humans and AI to understand work, decisions, evidence, authority and outcomes over time.
The Spine is not primarily an integration layer or data store. It is the semantic operating substrate through which organizational business becomes contextual, actionable and continuous.
2. Business Context drives everything
Business Context is not a database view, not a search index, not a record selector. It is the complete operating reality of the organization:
Mission · Objectives · Goals · KPIs · Initiatives
Organizations · Teams · People · Roles · Responsibilities
Customers · Accounts · Partners · Vendors · Products · Projects
Work · Tasks · Commitments · Lifecycle States · Dependencies
Relationships between entities and work
Events · Changes · Signals · Temporal History
Decisions · Rationale · Approvals · Authority Lineage
Evidence · Provenance · Source References
Policies · Capabilities · Execution Eligibility
Expected Outcomes · Actual Outcomes · Verification State
Every action in the system is grounded in this context:
User opens product → Business Context determines what matters now
Workbench composes → Business Context shapes the projection
Twin reasons → Business Context provides the objective and state
Agent takes work → Business Context provides the goal and authority
Governance evaluates → Business Context provides risk, policy and impact
Execution occurs → Business Context defines the capability being performed
Reconciliation closes → Business Context is what actually changed
Memory promotes → Business Context is what the organization now knows
The user should never have to "feed context to the system." The system already knows the business. The user works; context is already there.
3. Logical domains
The logical Business Context Spine carries three coupled domains:
Operational Truth. Entities, fields, relationships, lifecycle state, work state, decisions, approvals, expected outcomes, source ownership and reconciliation status.
Knowledge and Evidence. Documents, chunks, embeddings/search representations, citations, attachments, source artifacts and evidence references.
Business Memory and Continuity. Continuity runs, commitments, decisions, synthesized organizational context, promotion state, temporal history and organizational memory.
Personal Contextual Memory and AI Continuity Memory are NOT equal peers to Business Context. They are working continuities that serve it — personal working notes for the human, working state for the AI. Neither is organizational memory. Neither is the Spine. The Spine is the business context.
3. Logical truth before physical storage
The product architecture freezes the logical Spine contract, not one vendor-specific database. Physical implementation may use Postgres/D1, object storage, vector/search, event stores, caches and queues underneath the logical contract.
The Business Context Spine is the canonical logical authority. Physical storage authority is an implementation/deployment ADR and must not redefine product semantics.
4. Mandatory Base Spine and additive expansion
Every tenant receives a valid mandatory Base Spine. The Spine is not generated only from whichever connectors a customer happens to install.
Effective Spine
= Mandatory Base Spine
∪ Department Expansion
∪ Industry Expansion
∪ Role Expansion
∪ Connector Expansion
∪ Tenant Expansion
∪ Contextual Expansion
No expansion may remove tenancy, provenance, authority, evidence, lifecycle, sync or reconciliation contracts.
5. Business Intent and Lifecycle Above the Tools
Mission → Objectives → Goals → KPIs → Initiatives → Work → Decisions → Actions → Outcomes → Learning
The Business Context Spine links operating work back to this chain. Organizations operate through lifecycle transitions rather than static department silos alone:
Business Objective → Operating Lifecycle → Event → State Transition → SOP / Process
→ Activities → Records / Evidence → Human + AI Work → Decision / Approval
→ Execution → Verification → Memory → Next State
6. State-Plane Separation
| Plane | Purpose |
|---|---|
| Business Context Spine | Durable organizational operating truth and continuity. |
| Personal Contextual Memory | Human-specific working continuity. |
| AI Continuity Memory | Twin/agent working continuity. |
| Spine Cache | Disposable hydration/acceleration state. |
| Knowledge | Retrievable semantic representations linked to evidence. |
| Blobs | Raw files, payloads, exports, attachments and evidence artifacts. |
| Session Logs | Conversation, model/tool-call and interaction lifecycle. |
| Audit Logs | Identity, authority, approval, model/agent, capability, execution and outcome lineage. |
| Sync State | Cursors, checkpoints, retries, pending mutations, DLQ and conflicts. |
| Config State | Compiled tenant/provider/policy/composition/sync choices. |
| Ephemeral Runtime | Locks, leases, scratch state, temporary context and rate limits. |
Spine Cache can always be rebuilt from canonical state. Cache never becomes truth. Knowledge representations must retain evidence links. Raw sessions are evidence/history; only governed promotion creates durable organizational memory.
7. The feature test
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.
This is the clean test for future features, architecture decisions and product direction. If it does not connect to the Business Context Spine, it does not belong.