Business Context — The Semantic Foundation
Business Context is the Tier-0 semantic foundation of SpineWorkspace. Without it, nothing works.
What is Business Context?
Business Context is the complete, connected representation of organizational reality required to understand, decide, coordinate, execute, and continue business work.
It is not a database table. It is not a document. It is not a vector index. It is the semantic substrate that gives the entire workspace meaning.
Without Business Context, there is no SpineWorkspace. 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.
The Tier-0 Principle
Business Context is the semantic foundation of SpineWorkspace. It connects organizational business reality to Work, Humans, AI, Agents, Memory, Knowledge, Capabilities, Communication, Decisions, Governance, Execution, Evidence, Continuity and Outcomes.
This is not a feature. It IS the system.
BUSINESS CONTEXT
│
▼
Everything else
What Business Context Contains
Business Context contains or links to:
| Domain | Examples |
|---|---|
| Organization | Structure, departments, teams, functions |
| Goals & Objectives | Strategic priorities, KPIs, targets |
| People & Roles | Who does what, who decides what |
| Business Entities | Accounts, deals, tickets, contracts, projects |
| Relationships | How entities connect to each other |
| Events | What happened and when |
| Current State | What is true right now |
| Historical State | What was true before |
| Decisions | What was decided and why |
| Communications | Emails, messages, meeting notes |
| Evidence | Supporting data for claims |
| Policies | Rules, guardrails, governance |
| Work | What needs to happen |
| Outcomes | What actually happened |
The Fundamental Loop
Business Context participates in a continuous loop:
Business → Context → Work → Action → Outcome → Context
Not:
Application → AI → tool call → result
The second loop is exactly the fragmented model SpineWorkspace replaces.
Business Context vs Data
| Data | Business Context |
|---|---|
| Raw records from source systems | Connected, interpreted organizational reality |
| Provider schema | Canonical organizational schema |
| Fragmented across silos | Unified in the Business Context Spine |
| No inherent meaning | Meaning derived from organizational goals |
| Static snapshots | Continuous, evolving, looped |
Business Context vs Memory
Business Context IS the organization's memory. Personal Contextual Memory and AI Continuity Memory are working continuities that serve Business Context — they are not equal peers to it.
| Domain | What it is | Relationship to BC |
|---|---|---|
| Business Context | THE organization's memory | THE thing |
| Personal Contextual Memory | Human's working notes | Serves BC |
| AI Continuity Memory | Twin/agent working state | Serves BC |
How Business Context is Established
Business Context is established through:
- Ingestion — connecting to source systems
- Normalization — converting provider schemas to canonical primitives
- Entity Resolution — identifying duplicates, conflicts, relationships
- Contextualization — linking data to organization, domain, entity, Work, user, time
- Governance — determining whether results become evidence, state, or candidate memory
- Promotion — validated outcomes become Business Context through governed approval
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 test applies to every feature, capability, screen, and integration. If it cannot pass this test, it does not belong.