Full System Reference

What IntegrateWise is

IntegrateWise is the company. Spine Workspace is the product: a governed, self-organizing operational Workbench. A person works from one authenticated surface while the platform assembles permitted context from connected systems, preserves continuity, prepares work through Twin, and executes only through policy-bound capabilities.

One Workbench. One governed Spine. Many contextual projections. Truth you own; AI you rent; approval in between; verification before completion.

The boundaries that do not move

A host or subdomain can suggest a projection. It cannot decide tenant, user, role, policy, connection scope or capability authority.
Twin is contextual and non-authoritative. It may reason, prepare, explain and propose. It never self-approves, owns credentials or silently executes a consequential action.
Connector owns provider credentials and protocols. Browser, host, marketplace, Twin and public MCP clients do not receive those credentials.
Public marketing is separate from platform control. Brand Store, Book of Records and Org Memory are internal-only, not public marketing solution routes.
The public IW-Spine-Network MCP publishes exactly 19 semantic tools. The internal MCP Pool is never a public product interface.
A provider acknowledgement is not completion. Receipt/outcome must be re-ingested, reconciled and reflected in a refreshed projection.

The complete operating flow

Flow D: identity → tenant membership → consent → ConnectionBinding → policy → capability grant
          │
          ├─ Flow A/B: provider record, event, document or communication
          │            → Loader → Normalizer → Pipeline → canonical promotion
          │
          ├─ Flow C: Twin/model output → candidate, draft or proposal only
          │
          └─ Workbench projection → intent → Capability → Governance
                   → explicit approval for mutation → Hermes
                   → connector/provider/delegated action → receipt/outcome
                   → re-ingestion → reconciliation → promoted truth → refreshed projection

Storage authority

Store	Role	It is not
Neon/Postgres	Canonical business truth: entities, relationships, lineage, approvals, audit and promoted outcomes	A browser write target or disposable cache
D1	Tenant-bounded operational state and rebuildable projections	A second unrestricted canonical writer
KV	Hot/session/invalidation state	Durable truth
R2	Raw payloads, attachments and evidence blobs	Structured business truth
Vectorize / AI Search	Derived retrieval indexes	An authority that overrides canonical records

Workbench, role and projection model

The Workbench is the one authenticated product runtime. Its role, departmental, industry and entity-specific views are projections of the same governed platform—not separate applications, connector registries or databases.

Every projection must show truthful state: loading, empty, partial, connector degraded, MCP Pool unavailable, approval needed, queued, executing, observing, verified, failed or compensated. A live runtime failure may not become seeded/demo success.

Capability, governance and execution

intent → registered capability → policy/evidence → proposal
       → approval token when required → Hermes → provider/delegation
       → receipt → outcome re-ingestion → reconciliation → projection refresh

Governance evaluates authority. Hermes coordinates an already authorized execution. Pipeline promotes reconciled outcomes. No component can safely collapse those responsibilities.

Deployment ownership

Lifecycle	Browser/marketing	Trusted runtime	Purpose
Development	Local/Vercel development	Local Worker development	Engineering only
Customer Zero	Isolated preview or named environment	Cloudflare `test` environment	Internal dogfooding with isolated bindings/secrets
External	Vercel production environment	Cloudflare `prod` environment	Clean external tenants after full proof

Named Worker environments require their own explicit bindings. Test and production cannot share resource IDs, queues, service targets or secrets.

Release Readiness →Governance →Spine →Workbench →Source Intake →

Documentation Home Release Readiness