Unclassified

02 · Business Context View

Without Business Context, there is no meaningful SpineWorkspace. The semantic foundation that gives Work, AI, Agents, Memory, and Outcomes their meaning.

Without Business Context, There Is No SpineWorkspace

Business Context is Tier-0. It is not one input among many. It is the semantic substrate that gives the entire workspace meaning.

                    ORGANIZATIONAL BUSINESS
                              │
                              ▼
                 BUSINESS CONTEXT SPINE
               ───────────────────────────
                 The semantic substrate
               THE organization's memory
                              │
        ┌─────────────────────┼─────────────────────┐
        ▼                     ▼                     ▼
     Human Workbench     AI Workbench          Shared Work
        │                     │                     │
  Personal Memory       AI Continuity       Organizational
   (serves BC)           (serves BC)          Memory (THE)

What Business Context Is

Business Context is the connected representation of organizational business reality — what the business is, what it is trying to achieve, who is involved, what is happening, what was decided, and what should happen next.

It answers for every object or activity:

Object	Business Context question
People	Who is responsible and accountable?
Work	What business objective or outcome does it serve?
AI	Why is AI involved and what business context is it operating within?
Agents	What organizational role and responsibility does an agent represent?
Knowledge	What does the organization know about its business?
Memory	What continuity matters to the organization, person, or AI?
Capabilities	What can be done in service of the business?
Tools / ecosystems	Where does the underlying business information or action reside?
Communication	What business context does the conversation belong to?
Decisions	What was decided, by whom, under what authority?
Governance	What is permitted in this context?
Execution	What business action is being performed?
Evidence	What proves what actually happened?
Projection	What portion of reality should this participant see?
Continuity	What needs to persist so work can continue intelligently?

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.

What Business Context Contains

Business — mission, objectives, goals, KPIs, operating model
Entities — accounts, opportunities, cases, invoices, people, products, and their canonical types
Relationships — how entities connect (account → opportunity → work → outcome)
Goals & KPIs — what the organization is aiming at, how it measures progress
Knowledge — accumulated organizational knowledge, not just raw data
Decisions — what was decided, by whom, with what authority and evidence
Work — the common unit of activity that carries objective, context, and state
State — current and historical truth, with provenance
Evidence — what proves what happened (execution receipts, verification)
Organizational Memory — durable business memory that survives sessions, devices, and agents

Business Context vs. Spine vs. Memory

Term	Meaning
Business Context	The semantic concept — the connected business reality that gives everything meaning
Business Context Spine	The durable, governed substrate that holds Business Context — THE organization's memory
Organizational Memory	The durable business memory inside the Spine — what the organization accepts as truth
Personal Contextual Memory	The human's working continuity — operates on Business Context, does not replace it
AI Continuity Memory	The AI's working continuity — operates on Business Context, does not replace it

User thought ≠ AI inference ≠ Organizational truth

A personal memory item remains personal unless deliberately shared/promoted. An AI working item remains AI working continuity unless promoted through Triage / Governance / governed write path.

The Business Context Hierarchy

Level 1: Business Context
   ├── What business are we in?
   ├── What are our goals?
   └── What are our constraints?
         │
         ▼
Level 2: Domain Context
   ├── Account Success, Sales, Marketing, Support, Finance, Ops, Product & Eng, Founder/Exec …
   └── Each with canonical entities and relationships
         │
         ▼
Level 3: Work Context
   ├── Current Work, related entities, previous interactions, next steps
   └── Active Context Bundle for the participant
         │
         ▼
Level 4: Decision Context
   ├── Relevant data, past decisions, policies, suggestions, approvals
   └── What is needed to decide and to be audited after

How Business Context Becomes Truth

Business Context is not asserted. It is established through governed process:

External Systems
      │
      ▼
   Loader → Normalizer → Pipeline → Governed Writer
      │
      ▼
Business Context Spine
      │
      ▼
 Projection → Human Workbench / AI Workbench
      │
      ▼
   Work → Governance → Hermes → External System → Outcome
      │
      ▼
 Re-ingest → Verify → Reconcile → Update Spine → Rehydrate

Provider schema is never canonical. Every inbound record is normalized, deduplicated, linked, and governed before it can become Business Context.

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 filter for every surface, capability, agent, and integration.

Where to Go Next

The single mental model around this substrate.


How this context is projected to the human.


How the Spine holds entities, events, state, knowledge, and provenance.


Three domains — organizational as THE memory, personal and AI as serving continuities.

</CardGroup>