SpineWorkspace / IntegrateWise — Founder Canon
Version: 6.0.0 — Founder Canon
Date: 31 August 2026
Status: Canonical. This is the only document allowed to redefine the architecture. All other files must declare whether they are canonical, downstream implementation specifications, evidence/readiness reports or archived history.
Supersedes: 1 August 2026 GitHub canonical freeze where explicitly stated.
Scope: SpineWorkspace product, Human Workbench, AI Workbench, shared Business Context Spine, Personal Contextual Memory, AI Continuity Memory, Twin, Spine Agents, user experience, UI/AI context pipelines, OODA, platform infrastructure, capability execution, governance, continuity, distribution, implementation alignment and go-live doctrine.
One Workspace. All Connected Software. Business Context. Shared Work. Human + AI Working Together.
Humans govern. AI helps. Spine preserves continuity.
Tier-0: The Foundational 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.
This is the central anchor for the entire architecture. It sits above the Human Workbench / AI Workbench discussion, because it explains why those products exist in the first place.
SpineWorkspace is not a workspace with a Spine. It is a workspace constituted by the Business Context Spine.
Everything else derives from that.
The canonical hierarchy
ORGANIZATIONAL BUSINESS
│
▼
BUSINESS CONTEXT SPINE
───────────────────────────
The semantic substrate
│
┌───────────────────────┼───────────────────────┐
│ │ │
▼ ▼ ▼
HUMAN AI ORGANIZATION
│ │ │
▼ ▼ ▼
Human Workbench AI Workbench Shared Work
│ │ │
▼ ▼ ▼
Personal Contextual AI Continuity Organizational
Memory Memory Memory
│ │ │
└───────────────────────┼───────────────────────┘
│
▼
Contextualized Capabilities
Agents • Knowledge • Tools
Communication • Decisions
│
▼
GOVERNED EXECUTION
│
▼
OUTCOME / EVIDENCE / STATE
│
▼
RECONCILIATION → SPINE
The fundamental loop
Business → Context → Work → Action → Outcome → Context
Not:
Application → AI → tool call → result
The latter is exactly the fragmented model IntegrateWise is intended to replace.
Business Context is the semantic connective tissue
Every significant object or activity acquires meaning through its relationship to the business:
| Object | Business Context question |
|---|---|
| People | Who is responsible and accountable? |
| Work | What business objective, responsibility 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, and 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 the business 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.
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.
Five separate views
SpineWorkspace is one system experienced through five separate views. These are not the same thing and should not be conflated:
| View | What it is | Documented in |
|---|---|---|
| User View | Human Workbench — what the user sees and does | 01-PRODUCT-AND-EXPERIENCE.md §4A |
| Platform View | IntegrateWise Platform Console — what the operator manages | 06-IDENTITY-CONFIG-INTEGRATION-DISCOVERY-ACTIVATION.md |
| Package View | Product offering and packaging — what comes with which tier | Commercial product boundary |
| Pipeline View | Data flow — ingestion → normalization → four flows → governed writes | 07-INGESTION-FOUR-FLOWS-AND-GOVERNED-WRITES.md |
| Agentic View | AI/agent execution — Twin → Agents → Capabilities → Governance → Hermes | 04-AI-WORKBENCH-TWIN-AGENTS-AND-AI-MEMORY.md, 09-CAPABILITY-FABRIC-AND-ADK.md, 11-HERMES-EXECUTION-AND-PROVIDERS.md |
All five views share the same Business Context Spine. They do not share the same interface, concerns, or documentation.
0.1 Source precedence
When sources disagree, use this order:
- Founder decisions dated 31 August 2026 and the latest project conversations — highest authority for product, experience, memory boundaries, Human Workbench, AI Workbench and the human-AI operating model.
- Late-August SpineWorkspace consolidation decisions and master-system visual — authoritative design direction where they elaborate the founder decisions.
- 1 August 2026 GitHub canonical freeze — implementation baseline and retained technical contracts where not superseded.
- Earlier canonical/downstream architecture documents and code — evidence of implementation, migration state and historical design.
- External 2026 market research — validation of the category and design pressures only.
0.2 Constitutional memory rule
User thought ≠ AI inference ≠ Organizational truth
A Personal Contextual Memory item remains personal unless deliberately shared/promoted. An AI Continuity Memory item remains AI working continuity unless promoted through the appropriate Triage/Governance/write path. Organizational Memory is durable business memory only after the organization accepts it into the governed Business Context Spine.
0.3 Constitutional product rule
SPINEWORKSPACE
= Business Context as the semantic foundation of everything
+ Two projections over the same business reality (Human Workbench + AI Workbench)
+ Separate Human and AI Continuity (working states that serve Business Context)
+ Governed Work and Execution
Business Context is the semantic foundation
Business Context is not one input among many. It is the semantic substrate that gives the entire workspace meaning. Without Business Context, SpineWorkspace has no meaning; it becomes another collection of tools and interfaces.
The Spine is not simply an integration or data layer. It is the context layer that makes the rest of the system semantically coherent.
The correct hierarchy
ORGANIZATIONAL BUSINESS
│
▼
BUSINESS CONTEXT SPINE
│
┌───────────────────┼───────────────────┐
│ │ │
▼ ▼ ▼
WORKSPACE USERS AI
│ │ │
▼ ▼ ▼
Human Workbench Personal Context AI Continuity
│ │ │
└───────────────────┼───────────────────┘
│
▼
SHARED WORK
│
▼
CAPABILITIES / AGENTS / TOOLS
│
▼
GOVERNED EXECUTION
│
▼
OUTCOME / EVIDENCE / STATE
│
▼
BACK INTO BUSINESS CONTEXT
The critical loop
Business → Context → Work → Action → Outcome → Context
Not:
Workspace → tools → AI → memory
Business Context is the connective tissue
Every SpineWorkspace capability is contextualized against the business:
| Capability | Business Context question |
|---|---|
| Work | What business objective or responsibility does this work serve? |
| People | Who is responsible, involved, accountable or affected? |
| AI | Why is AI involved, and what business context does it operate on? |
| Agents | What organizational role and business responsibility does an agent serve? |
| Memory | What should be remembered because it matters to the business? |
| Knowledge | What organizational knowledge has accumulated? |
| Capabilities | What can be done in service of the business? |
| Tools / ecosystems | Where does the underlying business data or action live? |
| Communication | What business context does a message, update or decision belong to? |
| Decisions | What business decision was made, by whom, with what authority? |
| Governance | What is permitted in this business context? |
| Execution | What business action is being performed? |
| Evidence | What proves what actually happened? |
| Projections | What should this particular participant see from the underlying business reality? |
| Continuity | What context should persist for the organization, human or AI? |
The Workbenches are two projections over the same business reality
The Human Workbench and AI Workbench are not two independent applications. They are two projections over the same business reality:
BUSINESS CONTEXT SPINE
│
┌───────────┴───────────┐
│ │
HUMAN PROJECTION AI PROJECTION
│ │
▼ ▼
HUMAN WORKBENCH AI WORKBENCH
│ │
Personal Memory AI Continuity
│ │
└───────────┬───────────┘
│
SHARED WORK
│
▼
BUSINESS OUTCOMES
The user comes to SpineWorkspace because their work has meaning within a business context. The AI operates because there is business context, business work, business authority and a business outcome to support.
The three memory domains
| Domain | What it is | Role |
|---|---|---|
| Business / Organizational Memory | What the organization knows and what has become part of organizational reality | THE memory. The Spine. Without it, nothing works. |
| Personal Contextual Memory | What matters to the individual human while they operate on the business | Operates ON Business Context. Does not replace it. |
| AI Continuity Memory | What the AI needs to maintain continuity while helping with business work | Operates ON Business Context. Does not replace it. |
The deeper question for AI continuity is not "where do we store AI memory?" but: How does AI Continuity maintain its own continuity while remaining continuously grounded in the authoritative Business Context Spine?
The elevated product principle
Business Context is the semantic foundation of SpineWorkspace. It connects the organization's business reality to Work, Humans, AI, Agents, Memory, Knowledge, Capabilities, Communication, Governance, Execution, Evidence and Outcomes. Without Business Context, SpineWorkspace has no meaning; it becomes another collection of tools and interfaces.
Shorter:
The Spine gives work its business context.
This sits above the Human Workbench / AI Workbench discussion, because it explains why those products exist in the first place.
0.4 What this Canon supersedes
- Primary product identity. The product is SpineWorkspace. IntegrateWise is the infrastructure/platform powering it.
- Two first-class work environments. The system contains a Human Workbench and an AI Workbench operating over the same organizational business context.
- Human Workbench primacy. Human Workbench is the primary daily product for users.
- AI Workbench. AI has a first-class working environment over business context. It is not merely a chat panel, an API payload or the Twin itself.
- Three continuity scopes. Shared Business Context / Organizational Memory, Personal Contextual Memory and AI Continuity Memory are distinct in purpose, authority and lifecycle.
- Twin vs AI Workbench. Twin is the human-facing contextual AI coworker operating within the AI Workbench; Twin is not the complete AI operating environment.
- Spine Agents. Specialized agents operate as governed organizational actors with identity, authority, capability access, Work state, evidence and continuity.
- Shared Work is the coordination medium. Humans and agents hand off through durable Work/context/evidence state rather than re-explaining the organization in conversation.
- Experience is first class. UI composition, AI context composition and OODA are internal product machinery.
- No monolithic AI Orchestrator. Cognition, model routing, agent runtime, capability resolution, authority and execution remain separated.
- Verified closure. Provider success is not completion. The loop closes only after re-ingestion, verification, reconciliation, governed Spine update and rehydration of both Workbenches.
0.5 Final Master System Map
ORGANIZATIONAL BUSINESS
Mission · Objectives · Goals · KPIs
│
▼
BUSINESS CONTEXT SPINE
───────────────────────────
The semantic substrate
THE organization's memory
Without it, nothing works
│
┌───────────────────────┼───────────────────────┐
│ │ │
▼ ▼ ▼
HUMAN AI ORGANIZATION
│ │ │
▼ ▼ ▼
Human Workbench AI Workbench Shared Work
(BC Projection) (BC Projection) (Grounded in BC)
│ │ │
▼ ▼ ▼
Personal Contextual AI Continuity Organizational
Memory Memory Memory
(serves BC) (serves BC) (THE memory)
│ │ │
└───────────────────────┼───────────────────────┘
│
▼
Contextualized Capabilities
Agents • Knowledge • Tools
Communication • Decisions
│
▼
GOVERNED EXECUTION
│
▼
OUTCOME / EVIDENCE / STATE
│
▼
RECONCILIATION → SPINE
│
▼
BUSINESS CONTEXT UPDATED
│
▼
NEW AUTHORIZED PROJECTIONS
│
▼
HUMAN + AI WORKBENCH REHYDRATE
│
▼
NEXT WORK
0.6 Canonical Product Formula
SpineWorkspace
= Business Context Spine (THE semantic foundation — without it, nothing works)
+ Two projections over the same business reality
- Human Workbench + Personal Contextual Memory
- AI Workbench + AI Continuity Memory
+ Shared Work (grounded in Business Context)
+ Twin + Spine Agents (operating on Business Context)
+ Projection and Context Assembly
+ Capability Fabric (in service of Business Context)
+ Human/Policy Governance (protecting Business Context)
+ Hermes Execution (acting on Business Context)
+ Verification and Reconciliation (verifying Business Context changed)
+ Continuous Rehydration (updating Business Context)
Platform formula:
IntegrateWise Platform
= One Auth
+ Configuration
+ Integration Manager
+ Discovery
+ Activation
+ Gateway / Loader / Four Flows
+ Normalizer / Triage / Governed Writers
+ Business Context Spine Fabric (THE thing — everything else serves it)
+ Knowledge / Evidence / Memory / Cache / Events
+ Projection / Human UI / AI Context Assembly
+ Model Routing / ADK / Agents
+ Capability Fabric / Governance / Hermes
+ Sync / Verification / Reconciliation
+ Audit / Observability / Security / Tenancy
+ Distribution through Workbench, Continuity Bridge, MCP, APIs and SDKs
0.7 Final One-Sentence Definitions
SpineWorkspace: A self-organizing shared workspace where humans and AI work from the same governed business context, each with its own continuity memory, so humans can focus on judgment and responsibility while AI handles context assembly, preparation, coordination and permitted execution.
IntegrateWise: The infrastructure platform underneath SpineWorkspace that connects the organization's systems, preserves business context and continuity, projects the right context to humans and AI, and coordinates governed capability execution through verification and reconciliation.
The doctrine: Humans govern. AI helps. Spine preserves continuity.
0.8 Product acceptance tests
- A user can authenticate, bind to a tenant and connect controlled systems.
- Initial hydration produces a valid Business Context Spine rather than an empty shell.
- Human Workbench composes useful cross-tool context from the Spine.
- Personal Contextual Memory persists the user's working continuity without silently becoming organizational truth.
- AI Workbench/Twin receives authorized business context plus AI Continuity Memory.
- Twin can explain current work with evidence and prepare an action/proposal.
- A Spine Agent can take a subtask with identity, Work state, context and authority, then hand off without losing continuity.
- Capability Fabric can resolve a provider-neutral capability to an executable route.
- Governance can allow, deny or require approval based on identity/risk/policy.
- Hermes executes only an authorized plan and returns outcome evidence.
- The provider outcome is re-ingested, verified and reconciled.
- The Business Context Spine updates only through governed canonical writes.
- Both Human Workbench and AI Workbench rehydrate from the verified new state.
- The full chain is reconstructable through trace, approval, capability, execution, evidence and reconciliation lineage.
- A model, connector or agent can be replaced without losing the organization's continuity record.