Superseded

IntegrateWise / SpineWorkspace — Product Framing Lock

Status: SUPERSEDED BY FOUNDER CANON
Effective: 2026-08-25
Superseded by: docs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md (31 August 2026)
Scope: Product identity, business model, system narrative and terminology
Authority: This document is retained as historical reference. The Founder Canon is now the authoritative source for product framing and terminology.

This document is superseded. The 31 August 2026 Founder Canon (docs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md) is the authoritative source for product framing, terminology and architecture. This file is retained for migration reference only.

1. Company and product

TermCanonical meaning
IntegrateWiseThe company and platform builder.
integratewise.aiIntegrateWise company/platform domain.
SpineWorkspaceThe customer product and work environment built by IntegrateWise.
spineworkspace.comSpineWorkspace product domain.

Never use IntegrateWise as the product name. Never use SpineWorkspace as the company name.

2. Core product thesis

SpineWorkspace is the shared operational work environment where humans and AI work together toward business objectives using contextual business memory, governed work allocation and connected execution across the software a business already uses.

The central problem is not simply automation. Business work is fragmented across people, systems, communication channels, data stores and AI systems. SpineWorkspace coordinates that work while preserving context, authority, accountability and continuity.

3. Core value chain

Business Goals / Needs
        ↓
Fragmented Business Work
        ↓
Connected Systems
        ↓
Business Context Ingestion & Synthesis
        ↓
Spine Fabric
        ↓
Role / Domain / Responsibility Projection
        ↓
Human Workbench + Twin Workbench
        ↓
Human + Twin + Agents
        ↓
Governed Execution
        ↓
Source Systems
        ↓
Re-ingestion
        ↓
Verification / Reconciliation
        ↓
Governed Organizational Memory
        ↓
Better Context for Next Work

4. Spine Fabric

Spine is the contextual business-memory and operational-continuity substrate of SpineWorkspace.

It connects and preserves:

  • organizational context;
  • entities and relationships;
  • work and work state;
  • decisions and evidence;
  • events and timelines;
  • provenance and lineage;
  • operational state;
  • validated outcomes;
  • governed organizational memory.

Canonical Spine vs operational sandbox

The distinction is mandatory:

                 SPINE FABRIC
                       │
           ┌───────────┴───────────┐
           │                       │
    CANONICAL SPINE          OPERATIONAL SANDBOX
    governed truth           bounded working context
           │                       │
    organizational         Human/AI operational work
    memory + continuity    with governed context

AI does not receive unrestricted direct access to canonical organizational truth. AI operates on the governed operational context/sandbox derived from Spine.

5. Business Context Ingestion & Synthesis

The first system flow is:

Source Tools
   ↓
Connector / Ingestion
   ↓
Preprocessor
   ↓
Normalization / Identity Resolution
   ↓
Triage
   ↓
Context Assembly
   ↓
Spine Fabric

Triage classifies and routes information. It does not independently promote information into canonical organizational memory.

The governing principle is:

Triage classifies. Governance decides. Pipeline promotes. Spine owns organizational memory. Twin consumes governed context.

6. Projection model

The organization has one underlying business reality. Users do not receive separate copies of that reality.

Organization / Business Context
              ↓
         Spine Schema
              ↓
      Projection Engine
              ↓
   Role + Domain + Responsibility
   + Authority + Relevance + Policy
              ↓
        User Projection

The same organizational context can therefore appear differently to Sales, Finance, Operations, Engineering, HR, executives and other roles without duplicating canonical truth.

7. Human Workbench

The Human Workbench is the human operational surface of SpineWorkspace.

It projects the user's relevant business context and work rather than recreating every connected SaaS application.

Canonical experience areas include:

  • Today / Personal Work — what needs attention now;
  • Communications — relevant team and business communication;
  • Organization Memory / Knowledge — organizational documents, decisions, calls and retained context;
  • Work — the user's business work, entities, operational views and domain/KPI context.

The Workbench is adaptive through projections, not through separate products or separate truth stores.

8. Twin Workbench

Each user receives one Twin for their work.

The Twin is the user's AI work partner and coordination intelligence. It operates on governed operational context and can:

  • understand the current work;
  • assemble relevant context;
  • reason and propose;
  • coordinate work;
  • delegate bounded work to agents;
  • invoke governed capabilities;
  • monitor execution;
  • verify results;
  • report outcomes;
  • adapt future work from validated outcomes.

The Twin is not a second organizational authority and does not become the owner of canonical truth.

9. Coworker

Coworker is the contextual companion between active Human Workbench interaction and the Twin.

It gathers context from the user's active interaction, retrieves relevant information, assists communication and helps maintain continuity between what the user is doing and what the Twin needs to know.

Coworker is not a second orchestration authority.

10. Shared work allocation

Work is the primary coordination unit. Tasks are components of Work.

For each part of Work, SpineWorkspace can determine whether it should be performed by:

  • Human;
  • Twin;
  • Domain/specialist agent;
  • External agent;
  • Connected system/workflow;
  • Human + AI together.

Allocation considers capability, authority, responsibility, risk, complexity, context, urgency, cost, availability and policy.

11. Communication over the Bridge

The Bridge is the governed communication and execution boundary around Spine.

Human Workbench
      ↕
     Spine
      ↕
     Twin
      ↕
   Agents / Workflows
      ↕
MCP / ACP / ADK / Orchestrator
      ↕
Connected Tools / Services
  • MCP: AI ↔ tool/resource interaction.
  • ACP: governed agent ↔ agent/Twin contextual handoff.
  • ADK: agent development/runtime mechanism.
  • Orchestrator: coordinates durable execution, dependencies, retries, approvals and bounded agent work.

These are mechanisms of the platform. They are not the product's primary abstraction.

12. Execution and continuity loop

Execution is not complete merely because a tool returned success.

Need
 ↓
Goal
 ↓
Work Graph
 ↓
Context
 ↓
Projection
 ↓
Human / Twin
 ↓
Allocation
 ↓
Governance
 ↓
Execution
 ↓
Source System State
 ↓
Re-ingestion
 ↓
Verification
 ↓
Reconciliation
 ↓
Memory / Knowledge Promotion
 ↓
Next Work

The loop state must remain observable throughout the lifecycle.

13. How information becomes organizational knowledge

Processed source information becomes useful organizational knowledge through a governed lifecycle:

Source Data
  → Context
  → Work
  → Decision
  → Action
  → Outcome
  → Re-ingestion
  → Verification
  → Reconciliation
  → Governance
  → Memory Promotion
  → Organizational Knowledge

Memory is therefore not merely imported data. It is validated, contextualized and governed organizational knowledge that can improve future work.

14. Platform substrate

IntegrateWise provides the substrate required to run each unit of operational work, including:

  • identity and tenant boundary;
  • connected-system authority and discovery;
  • connectivity and connector projections;
  • contextual business memory and Spine infrastructure;
  • AI and agent runtime;
  • execution and orchestration;
  • communication bridge;
  • governance and policy enforcement;
  • MCP/ACP/ADK integration;
  • pipelines, synchronization and reconciliation;
  • observability and infrastructure.

The commercial/product model can therefore be expressed as:

IntegrateWise provides the infrastructure substrate; SpineWorkspace provides the business work environment.

15. Canonical terminology

TermDefinition
Business ContextConnected representation of the organization's relevant business reality.
Spine FabricContextual business-memory and operational-continuity substrate.
Canonical SpineGoverned organizational truth.
Operational SandboxBounded working representation exposed to AI/runtime participants.
WorkPrimary unit of coordinated business activity.
Work GraphConnected representation of objectives, work, entities, people, agents, actions, decisions and outcomes.
ProjectionRole/domain/responsibility/authority-specific view of shared business context.
Human WorkbenchHuman-facing operational work surface.
Twin WorkbenchAgentic work environment used by the user's Twin.
TwinUser-specific AI work partner and work coordinator.
CoworkerContextual companion for active Workbench interaction and communication.
Work AllocationDecision about who/what should perform each part of Work.
CapabilityGoverned statement of what can be done.
Execution FabricMechanisms that perform authorized work.
GovernanceAuthority, policy, risk, approval, evidence and accountability controls.
BridgeGoverned communication and execution boundary.
ReconciliationVerification that intended work produced the expected external/business state.
ContinuityPreservation of relevant context, state, decisions and progress across time, systems, people and AI.

16. Relationship to the technical architecture lock

This document locks product framing and terminology. It does not silently amend implementation contracts.

Where an implementation contract is frozen elsewhere, engineering must preserve that contract until the contract itself is explicitly changed and versioned.

The product framing target is therefore:

INTEGRATEWISE
Company / platform builder
        ↓
SPINEWORKSPACE
Customer product
        ↓
BUSINESS CONTEXT
        ↓
SPINE FABRIC
        ↓
PROJECTIONS
        ↓
HUMAN WORKBENCH + TWIN WORKBENCH
        ↓
BRIDGE / EXECUTION
        ↓
SOURCE SYSTEMS
        ↓
RE-INGESTION / RECONCILIATION
        ↓
ORGANIZATIONAL MEMORY
        ↓
NEXT WORK