Unclassified

IntegrateWise Documentation

Baseline: 2026-08-11
Authority routing: CANON.md

The documentation tree contains current specifications, implementation references, commercial material, runbooks, generated mirrors and historical evidence. File names alone do not establish authority.

Start here

  1. CANON.md — authority order and disposition rules.
  2. architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md — single canonical architecture.
  3. architecture/ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md — host identity/connector authority.
  4. architecture/SHARED_FRONTEND_SHELL_AND_DOMAIN_OWNERSHIP.md — common Auth + Connectors + MCP + Platform across every frontend.
  5. architecture/LIFECYCLE_CONTINUITY_AND_PROJECTION_MAP.md — phase/lifecycle/continuity-driven user flow and backend table → frontend projection map.
  6. architecture/PRODUCT_PACKAGE_RUNTIME.md — Product Package contracts.
  7. architecture/EXECUTION_MODE_TOOL_CAPABILITIES.md — Tool Capability Execution Mode.
  8. architecture/PLATFORM_MANAGEMENT_CONSOLE.md — operator/admin console.
  9. operations/GO_LIVE_SEQUENCE.md — release promotion and evidence gates.

Current product model

Host identity + host connections
→ One Auth
→ connector projections
→ Product Package
→ Shared Frontend Runtime
   Auth + Connectors + MCP + Platform
→ frontend-owned lifecycle/domain projection
→ Tool Capability
→ Governance
→ orchestrated execution
→ reconciliation
→ lifecycle transition + continuity update
→ Spine / Business Context
→ projection rehydrate

Product Package:

Discovery + Capabilities + Spine Cache + ADK + Orchestrator
+ Business Context + Loader + Normalizer + MCP Connector + Tool Capability

Platform Backend:

Package Control Plane + Services + AI + Agents + Memory + Pipelines

Frontend contract

Every frontend reuses:

Auth + Connectors + MCP + Platform

Each frontend may independently own the rest: domain navigation, routes, lifecycle views, UX, local presentation state and domain-specific projection composition.

Every frontend route must map back to backend canonical tables and declare its lifecycle, phase, continuity inputs, RBAC filters, projected capabilities, write path and rehydration trigger.

User/execution contract

Resume → Orient → Decide → Govern → Execute → Reconcile → Transition → Continue

Execution is lifecycle/phase-aware. A connector capability is exposed only when technically available, valid for the current business phase, allowed for the principal/RBAC scope and permitted by tenant policy.

Documentation classes

Canonical

Only architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md defines the complete architecture.

Normative focused contracts

The One Auth, Shared Frontend, Lifecycle/Continuity/Projection, Product Package, Execution Mode, Platform Management Console and Go-Live documents are normative for their bounded topics and subordinate to v2.2.

Active implementation references

Files under architecture/, specifications/, platform/, api/, operations/, runbooks/, playbooks/, wiki/, product/, commercial/, marketing/ and related directories may be used where they conform to the canonical baseline.

Historical / evidence

archive/, outbox/, internal/status/, architecture/source/ and files explicitly marked historical/superseded are lineage and evidence. They do not override current architecture.

Published mirror

apps/web/public/docs/** is a published copy of documentation. Source edits belong under docs/**; public copies should be generated or synchronized from the source tree.

Core invariants for documentation

  • One Auth is the ecosystem entry.
  • Host connectors remain host-owned; IntegrateWise stores governed projections, not copied provider credentials.
  • Every frontend shares Auth + Connectors + MCP + Platform runtime capabilities.
  • Remaining domain/product frontend UX may be independently owned.
  • Frontend surfaces project backend canonical tables; they do not create page-shaped truth stores.
  • User flow and execution are lifecycle-, phase- and continuity-driven.
  • Twin is contextual and non-authoritative.
  • Business Context/Spine owns governed operational truth; Memory does not.
  • Tool Capabilities are first-class executable contracts.
  • Every execution passes Governance.
  • Governance returns allowed, approval_required or blocked.
  • Approved/executed outcomes are reconciled, captured as evidence/audit, and may drive validated lifecycle/continuity updates.
  • Platform configuration, activation, integration, discovery and schema flows are connector-aware.

Operations

Key operational references:

Change rule

When a new document conflicts with v2.2, either change the proposal to conform or explicitly version the canonical architecture. Do not create another implicitly canonical FINAL, COMPLETE, LOCKED or CANONICAL document.