SpineWorkspace — Canonical Product Manual
THE DEFINITIVE END-STATE MODEL
This document is the frozen source of truth for all architecture, product, frontend, schema, and narrative decisions.
SUPERSEDED BY FOUNDER CANON for product/experience semantics. Seedocs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md(31 August 2026) as the authoritative source.
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. Without Business Context, SpineWorkspace has no meaning; it becomes another collection of tools and interfaces.
The Spine gives work its business context.
The Final Doctrine
IntegrateWise provides the infrastructure substrate. SpineWorkspace provides the business operating environment. Business Context is THE semantic foundation. The Business Context Spine IS the organization's memory — the connected representation of entities, work, state, relationships, events, decisions, evidence, provenance and memory. Each user receives an authorized projection of that organizational context through the Human Workbench, while their Twin operates in the AI Workbench to help understand, allocate, coordinate and execute work. The Communication Bridge enables governed exchange between Spine, humans, Twins, agents, workflows and connected systems through the appropriate runtime and communication mechanisms. Actions execute against the systems that remain authoritative, results are re-ingested and reconciled, loop state is updated, and validated outcomes become organizational memory and knowledge for the next work.
Deepest Abstraction
BUSINESS CONTEXT
↓
WORK
↓
HUMAN + AI
↓
EXECUTION
↓
RECONCILIATION
↓
KNOWLEDGE
↓
NEXT WORK
Spine preserves continuity across the entire loop.
The Final 18-Layer Stack
| Layer | Canonical Concept |
|---|---|
| 0 | Organization |
| 1 | Goals / Needs / Objectives |
| 2 | Business Context |
| 3 | Context Ingestion & Synthesis |
| 4 | Business Context Spine |
| 5 | Organizational Memory |
| 6 | Work Graph |
| 7 | Projection & Context Assembly |
| 8 | Human Workbench |
| 9 | AI Workbench (Twin + Agents) |
| 10 | Work Allocation |
| 11 | Governance |
| 12 | Communication Bridge |
| 13 | ADK / Orchestrator / ACP / MCP |
| 14 | Agent Fabric |
| 15 | Execution Fabric |
| 16 | Source Systems |
| 17 | Re-ingestion |
| 18 | Reconciliation |
| 19 | Loop State |
| 20 | Memory / Knowledge Promotion |
| 21 | Next Work |
Master Diagram
ORGANIZATION
│
▼
GOALS / NEEDS / OBJECTIVES
│
▼
BUSINESS CONTEXT
│
┌────────────────┴────────────────┐
│ │
PEOPLE / RESPONSIBILITIES BUSINESS SYSTEMS
│ │
└────────────────┬────────────────┘
▼
CONTEXT INGESTION
│
┌────────────────┴────────────────┐
│ │
Pre-processing Discovery
Normalization Connectors
Entity Resolution Events
Classification Files
Synthesis APIs
│ │
└────────────────┬────────────────┘
▼
BUSINESS CONTEXT SPINE
│
┌────────────────┼────────────────┐
│ │ │
Canonical Context Work Graph Org Memory
│ │ │
├────────────────┼────────────────┤
│ │ │
State Decisions Evidence
│ │ │
└────────────────┼────────────────┘
▼
PROJECTION / CONTEXT ASSEMBLY
│
┌───────────────┴────────────────┐
│ │
HUMAN WORKBENCH AI WORKBENCH
│ │
│ Twin + Agents │
│ │
└─────────────┼──────────────────┘
▼
WORK
│
WORK ALLOCATION
│
┌─────────────┼─────────────┐
│ │ │
HUMAN TWIN AGENT
│ │ │
└─────────────┼─────────────┘
▼
GOVERNANCE
│
▼
COMMUNICATION BRIDGE
│
Spine + ADK + Orchestrator + ACP
│
┌──────────┼──────────┐
│ │ │
MCP Workflows APIs
│ │ │
└──────────┼──────────┘
▼
EXECUTION FABRIC
│
▼
SOURCE SYSTEMS
│
▼
RESULT / EVENT
│
▼
RE-INGESTION
│
▼
RECONCILIATION
│
▼
LOOP STATE UPDATE
│
▼
BUSINESS CONTEXT SPINE
│
▼
KNOWLEDGE
│
▼
NEXT WORK
Company vs Product
IntegrateWise — Company + Platform Infrastructure
Identity
Connectivity
AI Infrastructure
Agent Runtime
Communication
Governance
Execution Infrastructure
Developer Platform
Connector Ecosystem
SpineWorkspace — Customer Product / Operating Environment
Business Context
Business Context Spine
Work
Work Graph
Projections
Human Workbench
AI Workbench
Twin + Spine Agents
Organizational Memory
Work Allocation
Domain Work
Business KPIs
Communications
Execution
Reconciliation
Continuity
Critical Architectural Boundaries
Canonical → Operational Boundary (INVARIANT)
SPINE
│
┌────────┴────────┐
│ │
CANONICAL PROJECTION
TRUTH │
│ ▼
│ CONTEXT ASSEMBLY
│ │
│ ▼
│ SANDBOX /
│ OPERATIONAL CONTEXT
│ │
└───────┐ ┌───┘
│ │
HUMAN AI
│
TWIN
│
AGENTS
AI does NOT receive unrestricted canonical organizational memory.
Canonical Spine
↓
Authorized Projection
↓
Context Assembly
↓
Operational Context / Sandbox
↓
Twin / Agent
Twin Scope
- Twin is the sole user-facing orchestrator
- Operates in the AI Workbench
- Works WITH human, not instead of
- Receives authorized projections only
- Operates on Business Context, not raw data
AI Workbench Scope
Human
↓
Human Workbench
↓
Business Context
↓
AI Workbench
│
├── Twin
│ ├── Business Context Understanding
│ ├── Work Allocation
│ ├── Agent Coordination
│ └── Governance
│
└── Spine Agents
├── Domain Agents
├── Specialist Agents
├── Research Agents
└── Workflow Agents
Twin coordinates work; Agents execute bounded tasks on Business Context.
Work Graph
Work is the primary coordination unit (not tasks).
BUSINESS GOAL
↓
WORK
↓
WORK GRAPH
│
├── Tasks
├── Decisions
├── Actions
├── Communications
├── Approvals
├── Dependencies
├── Exceptions
├── Human activity
└── AI activity
Work Allocation
For every piece of work:
WHAT NEEDS TO HAPPEN?
↓
WHO / WHAT SHOULD DO IT?
Decision factors:
Capability · Authority · Responsibility · Risk · Complexity
Context · Urgency · Cost · Availability · Policy
Human preference · Historical performance
Possible allocation:
HUMAN · AI/TWIN · SPECIALIST AGENT · WORKFLOW · SYSTEM · HUMAN + AI
Governance Model
Human-governed. Every consequential action follows:
Human or Twin intent
↓
Context and evidence assembly
↓
Capability resolution
↓
Policy evaluation
↓
Allowed / Approval Required / Blocked
↓
Governed execution
↓
Result and verification
↓
Reconciliation
↓
State, evidence and memory update
Loop State
IDENTIFIED
↓
CONTEXTUALIZED
↓
DEFINED
↓
ALLOCATED
↓
DECIDING
↓
EXECUTING
↓
OBSERVING
↓
RECONCILING
↓
LEARNING
↓
NEXT WORK
How Data Becomes Knowledge
SOURCE DATA
↓
INGESTION
↓
NORMALIZATION
↓
ENTITY RESOLUTION
↓
CONTEXTUALIZATION
↓
SPINE
↓
WORK / DECISION / ACTION
↓
EXECUTION
↓
OBSERVED RESULT
↓
RE-INGESTION
↓
RECONCILIATION
↓
EVIDENCE
↓
PATTERN
↓
GOVERNED PROMOTION
↓
ORGANIZATIONAL MEMORY
↓
KNOWLEDGE
Data does not become organizational knowledge merely because it entered Spine.
It becomes knowledge through context + experience + outcome + evidence + validation.
Communication Bridge
BUSINESS CONTEXT SPINE
│
▼
COMMUNICATION BRIDGE
│
┌────────────────┼────────────────┐
│ │ │
ADK ORCHESTRATOR ACP
│ │ │
└────────────────┼────────────────┘
│
Agent / Work Context
│
┌──────────┼──────────┐
│ │ │
MCP Workflow API
│ │ │
└──────────┼──────────┘
▼
EXECUTION FABRIC
| Component | Role |
|---|---|
| Business Context Spine | THE organization's memory and semantic foundation |
| Bridge | Controlled communication and context exchange |
| ADK | Agent development and runtime abstraction |
| Orchestrator | Coordinates context, intelligence, work, and capabilities |
| ACP | Agent-to-agent and Twin-to-agent communication |
| MCP | AI-to-tool and AI-to-resource communication |
| Execution Fabric | Mechanisms that perform actions in systems |
| Governance | Authority, policy, risk, approval, evidence, and audit |
Source Systems
SpineWorkspace does NOT replace:
- CRM (Salesforce, HubSpot)
- Documentation (Google Drive, Notion, Coda, Confluence)
- Communication (Slack, Teams)
- ERP, billing, finance, support, product systems
SPINEWORKSPACE
│
▼
GOVERNED ACTION
│
▼
SOURCE SYSTEM
│
▼
ACTUAL RESULT
│
▼
RE-INGEST
Reconciliation
Execution success ≠ business success.
INTENDED ACTION
↓
EXECUTION
↓
SOURCE RESULT
↓
OBSERVED STATE
↓
RECONCILIATION
│
├── Matched
├── Partial
├── Failed
├── Conflicting
└── Requires human review
Then:
RECONCILIATION
↓
LOOP STATE
↓
SPINE
↓
MEMORY
GTM Statements
One-line company
IntegrateWise builds the governed infrastructure that lets humans, AI, workflows, and connected systems work together around shared Business Context.
One-line product
SpineWorkspace is the Business Context-driven human-AI work environment where people and AI turn connected software into shared context, coordinated work, governed execution, and organizational continuity.
Short pitch
Most organizations have plenty of software and increasingly plenty of AI, but their work is still fragmented. Context sits across CRM, communication, documents, finance, support, product, and project tools; people spend their time assembling the story, coordinating handoffs, and repeating routine work.
SpineWorkspace sits above that ecosystem. It creates a shared Business Context and work layer where each person sees what matters for their role, their current work, and their authority. Their AI Twin works alongside them to gather context, prepare work, coordinate routine tasks, and execute approved actions through the existing systems of record.
Every result is re-ingested and reconciled, so the organization retains the evidence, outcome, and learning needed for the next decision. Humans govern the business. AI helps the business work. Spine preserves continuity.
Customer-facing
Your software stays. Your work comes together.
SpineWorkspace connects to the systems your business already uses and assembles the right context, tasks, decisions, communications, and actions around the work in front of you. Your AI Twin helps prepare and coordinate work, while you retain control over priorities, commitments, and approvals. Every action is governed, reconciled, and carried forward as Business Context.