01 · SpineWorkspace — Top View
The single mental model: Organizational Business → Business Context Spine → Human Workbench + AI Workbench → Shared Work → Outcome → Verify → Spine.
What Is the Whole Thing?
SpineWorkspace is not a workspace with a Spine. It is a workspace constituted by the Business Context Spine.
ORGANIZATIONAL BUSINESS
Mission · Objectives · Goals · KPIs
│
▼
BUSINESS CONTEXT SPINE
─────────────────────────────────
The semantic substrate
THE organization's memory
Without it, nothing works
│
┌────────────────────┼────────────────────┐
▼ ▼ ▼
HUMAN AI AGENTS
│ │ │
▼ ▼ ▼
HUMAN WORKBENCH AI WORKBENCH SPINE AGENTS
(BC Projection) (BC Projection) (Grounded in BC)
│ │ │
Personal Contextual AI Continuity Agent
Memory Memory Continuity
(serves BC) (serves BC) (serves BC)
│ │ │
└────────────────────┼────────────────────┘
▼
SHARED WORK
The coordination medium
│
▼
BUSINESS OUTCOME
│
▼
VERIFY → RECONCILE → SPINE
│
▼
BUSINESS CONTEXT UPDATED
│
▼
NEW AUTHORIZED PROJECTIONS
│
▼
HUMAN + AI WORKBENCH REHYDRATE
Business Context is Tier-0. It connects organizational business reality to Work, Humans, AI, Agents, Memory, Knowledge, Capabilities, Communication, Decisions, Governance, Execution, Evidence, Continuity and Outcomes. Without Business Context, SpineWorkspace has no meaning; it becomes another collection of tools and interfaces.
The One-Line Anchor
SpineWorkspace is a self-organizing workspace over the Business Context Spine, where humans and AI work on the same business reality with separate continuity.
Corporate parent: IntegrateWise is the infrastructure platform underneath SpineWorkspace.
The Fundamental Loop
Business → Context → Work → Action → Outcome → Context
Not:
Application → AI → tool call → result
The second loop is the fragmented model IntegrateWise replaces. The first loop is why Work, not chat, is the coordination medium.
Five Separate Views
One system, five views. They share the same Spine; they do not share the same interface.
| View | What it is | Lives in |
|---|---|---|
| User View | Human Workbench — what the user sees and does | Workspace Experience |
| Platform View | Platform Console — what the operator manages | Platform Execution |
| Package View | Product offering and packaging — tier boundary | Commercial boundary |
| Pipeline View | Data flow — ingestion → normalization → four flows → governed writes | Pipeline |
| Agentic View | Twin → Agents → Capabilities → Governance → Hermes | AI Workbench |
All five trace back to the same Business Context Spine.
What Lives Where
<CardGroup cols={2}>The semantic foundation. Entities, relationships, goals, KPIs, decisions, evidence.
The common unit of activity. Ownership, state, handoffs, human/AI participation.
Humans govern, AI helps, Twin is the coworker, Spines Agents are organizational actors.
How IntegrateWise actually runs business work end-to-end.
Invariants (from Founder Canon)
- SpineWorkspace = Business Context Spine (THE semantic foundation) + two projections over the same reality (Human Workbench + AI Workbench) + Shared Work + Twin + Spine Agents + Projection + Capability Fabric + Governance + Hermes + Verification/Reconciliation + Rehydration.
- Three continuity scopes — Organizational Memory (THE memory, in the Spine), Personal Contextual Memory, AI Continuity Memory. The latter two operate on and serve the first.
- Constitutional memory rule:
User thought ≠ AI inference ≠ Organizational truth - Verified closure: Provider success is not completion. Loop closes only after re-ingest → verify → reconcile → governed Spine update → rehydration.
- 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.
Where to Go Next
[Business Context View](/spineworkspace/business-context) — the semantic substrate that gives everything else meaning.
[Workspace Experience](/spineworkspace/workspace-experience) — the architecture disappears behind the experience.
[Pipeline View](/work/pipeline-view) — the most important technical/product view.