IntegrateWise Documentation

Spine Workspace: one governed workbench

IntegrateWise is the company. Spine Workspace is the product: one authenticated operational Workbench with contextual projections over a governed Spine.

The product brings permitted context from connected systems into the work at hand. Twin prepares and proposes; policy and people govern consequential changes; Hermes coordinates approved execution; outcomes are re-ingested and reconciled before the Workbench represents completion.

Promise: Truth you own. AI you rent. Approval in between. Verification before completion.

authenticated Workbench

many contextual projections

governed flows

D authority · A/B ingest · C candidate

public MCP tools

internal pool stays private

provider credentials in UI

Connector boundary only

⚠️

Evidence discipline: architecture describes what must be true. Only current code/configuration checks, deployed-provider inspection and end-to-end tests establish what is actually live. See Release Readiness.

Start here

Start your journey with IntegrateWise in three steps:

Read the current system reference

Start with Full System Reference for the product, flows, storage, Workbench, MCP, governance and deployment model.

Check whether a capability is ready

Use Release Readiness to distinguish verified configuration from runtime proof and see the remaining external-release blockers.

Understand source authority

Use Source Intake & Authority before applying historical architecture, commercial or source-library material.

Or, dive straight into the frozen reference:

The source of truth is the current repository architecture. This site is the navigable team portal; historical references remain useful only where they do not conflict with current authority.

Full System Reference →Release Readiness →Source Intake →Onboarding →Activation Hub →User Journey →Universal Spine →Workbench →Platform Backend →Canonical Reference →Repo Map →Governance →Commit Risk Memo →

Product and runtime in one view

#	Layer	Role
1	Flow D / One Auth	Server-derived principal, tenant membership, consent, ConnectionBinding, policy and capability grants.
2	Ingestion	Flow A/B provider and document signals enter through Connector, Loader, Normalizer and Pipeline.
3	Spine	Neon canonical business truth; D1 bounded operational state; KV/R2/retrieval indexes are supporting substrates.
4	Workbench + Twin	One authenticated Workbench renders bounded projections; Twin reasons and proposes without authority.
5	Governed execution	Capability → Governance → approval where needed → Hermes → provider/delegation → receipt → reconciliation.

web — User Workbench (the product)
one-access — OneAuth entry
platform — Platform Control Surface
marketing → www
docs — this site
mobile / desktop — Workbench channels

Product Package — reusable contracts

Platform Backend — Workers, pipelines, agents

Neon + D1 + KV + R2 + Vectorize + DO

The first release rule

No deployment is complete because a local build or static configuration check passes. The release must prove Flow D, isolated Customer Zero, canonical promotion, governed execution, receipt, reconciliation and a user-visible readback.

How This Site is Built

This site is built with Nextra (opens in a new tab) from shuding/nextra-docs-template (opens in a new tab) — Next.js + MDX with nextra-theme-docs.

pnpm i
pnpm dev   # → http://localhost:3000
pnpm build

Built 2026-08-20 · Nextra 4 · Theme nextra-theme-docs

Full System Reference