Unclassified

SpineWorkspace — Clean Documentation System

Company: IntegrateWise
Company domain: integratewise.ai
Product: SpineWorkspace
Product domain: spineworkspace.com
Canon: docs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md (31 August 2026 Founder Canon)

Documentation principle

The documentation system is divided by audience and authority:

docs/canonical/
  The single source of truth. 31 August 2026 Founder Canon.
  All other files must declare whether they are canonical, downstream
  implementation specs, evidence/readiness reports or archived history.

public/
  What customers/partners need to understand and use.

internal/
  Product doctrine, strategy, architecture, business and organizational memory.

development/
  Schemas, contracts, runtime, connectors, agents, APIs and implementation architecture.

guides/
  Task-oriented instructions for users, developers and operators.

sops/
  Repeatable operational procedures and incident/runbook instructions.

meta/
  Coverage, disposition and documentation governance.

archive/
  Historical/source material disposition; never a current authority by default.

The product hierarchy

BUSINESS CONTEXT SPINE
The semantic substrate · THE organization's memory
Without it, nothing in SpineWorkspace has meaning
  │
  │── HUMAN WORKBENCH (BC Projection for the human)
  │     └── Personal Contextual Memory (working state that serves BC)
  │
  │── AI WORKBENCH (BC Projection for AI)
  │     ├── Twin (contextual human-facing cognitive co-worker)
  │     ├── Spine Agents (governed organizational AI workers)
  │     └── AI Continuity Memory (working state that serves BC)
  │
  │── SHARED WORK (grounded in BC, the coordination medium)
  │
  │── Contextualized Capabilities / Agents / Knowledge / Tools / Communication / Decisions
  │
  │── GOVERNED EXECUTION
  │
  │── OUTCOME / EVIDENCE / STATE
  │
  │── RECONCILIATION → SPINE (the critical loop: Business → Context → Work → Action → Outcome → Context)
  │
  └── ORGANIZATIONAL MEMORY (THE memory — what the organization now knows)

INTEGRATEWISE PLATFORM (infrastructure that makes BC connect, persist, project, execute and reconcile)
  │
  ├── One Auth / Configuration / Integration Manager
  ├── Discovery / Activation Bridge
  ├── Gateway / Loader / Four Flows (A-B-C-D)
  ├── Normalizer / Triage / Governed Spine Writers
  ├── Projection Engine / UI Composition / AI Context Assembly
  ├── Capability Fabric / ADK / Model Routing
  ├── Governance / Hermes (execution coordination)
  ├── Sync / Verification / Reconciliation
  ├── IW Spine Network MCP / MCP Pool / Continuity Bridge
  └── Audit / Observability / Security / Tenancy

Five separate views

SpineWorkspace is one system experienced through five separate views. These are not the same thing:

View	What it is	Canonical ref
User View	Human Workbench — what the user sees and does	`01` §4A
Platform View	IntegrateWise Platform Console — what the operator manages	`06`
Package View	Product offering and packaging — what comes with which tier	Commercial boundary
Pipeline View	Data flow — ingestion → normalization → four flows → governed writes	`07`
Agentic View	AI/agent execution — Twin → Agents → Governance → Hermes → Reconciliation	`04`, `09`, `11`

All five views share the same Business Context Spine. They do not share the same interface, concerns, or documentation.

Documentation authority

1. Founder Canon (docs/canonical/00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md)
2. Canonical supplements (docs/canonical/01 through 18)
3. Architecture / Technical contracts
4. Implementation evidence
5. Guides / SOPs
6. Public marketing content

No implementation report, generated audit or historical snapshot overrides the Founder Canon.

Documentation principle

The product hierarchy

Five separate views

Documentation authority

Canonical navigation