IntegrateWise Documentation Canon

Status: Canonical routing index
Updated: 2026-08-11
Architecture authority: architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md

This page defines documentation authority and disposition. It does not create a second architecture.

Authority order

Order	Source	Governs
1	INTEGRATEWISE_ARCHITECTURE_v2.2.md	Product/platform boundaries, truth/authority model, runtime sequence, One Auth, shared frontend runtime, lifecycle/continuity projections, Tool Capability execution and Platform Backend.
2	ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md	Host-controlled identity, connector ownership, connector projections and delegated execution.
3	SHARED_FRONTEND_SHELL_AND_DOMAIN_OWNERSHIP.md	Common Auth + Connectors + MCP + Platform runtime shared by every frontend, with independent ownership of remaining domain/product UX.
4	LIFECYCLE_CONTINUITY_AND_PROJECTION_MAP.md	Phase/lifecycle/continuity-driven user flow, backend table → Projection Engine → frontend map, phase-aware capabilities and write/rehydration rules.
5	PRODUCT_PACKAGE_RUNTIME.md	Discovery, Capabilities, Spine Cache, ADK, Orchestrator, Business Context, Loader, Normalizer, MCP Connector and Tool Capability contracts.
6	EXECUTION_MODE_TOOL_CAPABILITIES.md	Execution Mode, policy states, dry-run/live execution, proposals, approvals, evidence and reconciliation.
7	PLATFORM_MANAGEMENT_CONSOLE.md	Operator/admin navigation, module responsibilities and connector-aware routing constraints.
8	operations/GO_LIVE_SEQUENCE.md	Development → Customer Zero → Customer Production promotion and evidence gates.

Detailed implementation specifications remain authoritative only for their local contract where they do not conflict with the sources above.

Current product truth

• Ecosystem entry: One Auth.
• Shared frontend contract: every frontend consumes the same Auth + Connectors + MCP + Platform runtime; the remaining domain/product UX may be independently owned.
• User Workbench: composed by role, subdomain, lifecycle, phase, backend truth and continuity context.
• Frontend truth rule: frontend routes are projections over backend canonical tables/relationships; they do not own page-shaped truth stores.
• User flow: Resume → Orient → Decide → Govern → Execute → Reconcile → Transition → Continue.
• Twin: contextual Workbench capability; never independent truth or execution authority.
• 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.
• Platform operator surface: Platform Management Console.
• Connector model: host-owned connection → governed IntegrateWise projection. Provider secrets are not replicated into projections.
• Canonical business truth: governed Neon/Postgres records written through approved writer/pipeline contracts.
• Operational cache/state: bounded, reconstructable D1/KV state.
• Evidence bytes: object storage where required, with governed metadata and lineage.
• Execution: phase-valid Tool Capability → Governance → (allowed | approval_required | blocked) → orchestrated execution → audit/evidence → reconciliation → lifecycle/continuity update.
• Environment progression: Development → Customer Zero → Customer Production with strict tenant/data/credential/runtime isolation.

Governance semantics

Governance is mandatory on every invocation. Approval is policy-dependent:

allowed            → execute under explicit pre-authorized policy
approval_required  → proposal → scoped human approval → execute
blocked            → deny

Consequential external mutations should default to approval_required. allowed is not a bypass; it is an explicit governed policy decision for a narrowly bounded operation.

Classification

• docs/architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md is the single canonical architecture document.
• The focused architecture files named in the Authority order are subordinate normative contracts.
• Other docs/architecture/**, docs/specifications/**, docs/wiki/**, docs/platform/**, docs/api/**, runbooks and playbooks are active only where they conform to the canonical baseline.
• docs/archive/**, docs/outbox/**, docs/internal/status/**, docs/architecture/source/** and other explicitly historical/superseded files are evidence/lineage, not authority.
• apps/web/public/docs/** is a published mirror. It is never the source of truth; generation/sync must originate from docs/**.
• A filename or title containing canonical, final, complete, lock or frozen does not override this index.

Superseded authority claims

The following are retained for lineage but no longer lead the authority chain:

• ARCHITECTURE_LOCK.md
• IMPLEMENTATION_CONTRACT_v1.1.md
• CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md
• earlier canonical/final architecture files

Where those files contain still-valid implementation detail, that detail remains usable only if it conforms to v2.2.

See README.md for the documentation map and repository policy.