{"slug":"business/CANON","title":"IntegrateWise Documentation Canon","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/CANON.mdx","bytes":7148,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Status:** Canonical routing index  \n> **Updated:** 2026-08-11  \n> **Architecture authority:** [`architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md`](architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md)\n\nThis page defines documentation authority and disposition. It does not create a second architecture.\n\n## Authority order\n\n| Order | Source                                                                                                        | Governs                                                                                                                                                                                    |\n| ----- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| 1     | [`INTEGRATEWISE_ARCHITECTURE_v2.2.md`](architecture/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. |\n| 2     | [`ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md`](architecture/ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md)             | Host-controlled identity, connector ownership, connector projections and delegated execution.                                                                                              |\n| 3     | [`SHARED_FRONTEND_SHELL_AND_DOMAIN_OWNERSHIP.md`](architecture/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.                                                     |\n| 4     | [`LIFECYCLE_CONTINUITY_AND_PROJECTION_MAP.md`](architecture/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.                                       |\n| 5     | [`PRODUCT_PACKAGE_RUNTIME.md`](architecture/PRODUCT_PACKAGE_RUNTIME.md)                                       | Discovery, Capabilities, Spine Cache, ADK, Orchestrator, Business Context, Loader, Normalizer, MCP Connector and Tool Capability contracts.                                                |\n| 6     | [`EXECUTION_MODE_TOOL_CAPABILITIES.md`](architecture/EXECUTION_MODE_TOOL_CAPABILITIES.md)                     | Execution Mode, policy states, dry-run/live execution, proposals, approvals, evidence and reconciliation.                                                                                  |\n| 7     | [`PLATFORM_MANAGEMENT_CONSOLE.md`](architecture/PLATFORM_MANAGEMENT_CONSOLE.md)                               | Operator/admin navigation, module responsibilities and connector-aware routing constraints.                                                                                                |\n| 8     | [`operations/GO_LIVE_SEQUENCE.md`](operations/GO_LIVE_SEQUENCE.md)                                            | Development → Customer Zero → Customer Production promotion and evidence gates.                                                                                                            |\n\nDetailed implementation specifications remain authoritative only for their local contract where they do not conflict with the sources above.\n\n## Current product truth\n\n- **Ecosystem entry:** One Auth.\n- **Shared frontend contract:** every frontend consumes the same Auth + Connectors + MCP + Platform runtime; the remaining domain/product UX may be independently owned.\n- **User Workbench:** composed by role, subdomain, lifecycle, phase, backend truth and continuity context.\n- **Frontend truth rule:** frontend routes are projections over backend canonical tables/relationships; they do not own page-shaped truth stores.\n- **User flow:** Resume → Orient → Decide → Govern → Execute → Reconcile → Transition → Continue.\n- **Twin:** contextual Workbench capability; never independent truth or execution authority.\n- **Product Package:** Discovery + Capabilities + Spine Cache + ADK + Orchestrator + Business Context + Loader + Normalizer + MCP Connector + Tool Capability.\n- **Platform Backend:** Package Control Plane + Services + AI + Agents + Memory + Pipelines.\n- **Platform operator surface:** Platform Management Console.\n- **Connector model:** host-owned connection → governed IntegrateWise projection. Provider secrets are not replicated into projections.\n- **Canonical business truth:** governed Neon/Postgres records written through approved writer/pipeline contracts.\n- **Operational cache/state:** bounded, reconstructable D1/KV state.\n- **Evidence bytes:** object storage where required, with governed metadata and lineage.\n- **Execution:** phase-valid Tool Capability → Governance → (`allowed` | `approval_required` | `blocked`) → orchestrated execution → audit/evidence → reconciliation → lifecycle/continuity update.\n- **Environment progression:** Development → Customer Zero → Customer Production with strict tenant/data/credential/runtime isolation.\n\n## Governance semantics\n\nGovernance is mandatory on every invocation. Approval is policy-dependent:\n\n```text\nallowed            → execute under explicit pre-authorized policy\napproval_required  → proposal → scoped human approval → execute\nblocked            → deny\n```\n\nConsequential external mutations should default to `approval_required`. `allowed` is not a bypass; it is an explicit governed policy decision for a narrowly bounded operation.\n\n## Classification\n\n- `docs/architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md` is the single canonical architecture document.\n- The focused architecture files named in the Authority order are subordinate normative contracts.\n- Other `docs/architecture/**`, `docs/specifications/**`, `docs/wiki/**`, `docs/platform/**`, `docs/api/**`, runbooks and playbooks are active only where they conform to the canonical baseline.\n- `docs/archive/**`, `docs/outbox/**`, `docs/internal/status/**`, `docs/architecture/source/**` and other explicitly historical/superseded files are evidence/lineage, not authority.\n- `apps/web/public/docs/**` is a published mirror. It is never the source of truth; generation/sync must originate from `docs/**`.\n- A filename or title containing `canonical`, `final`, `complete`, `lock` or `frozen` does not override this index.\n\n## Superseded authority claims\n\nThe following are retained for lineage but no longer lead the authority chain:\n\n- `ARCHITECTURE_LOCK.md`\n- `IMPLEMENTATION_CONTRACT_v1.1.md`\n- `CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md`\n- earlier canonical/final architecture files\n\nWhere those files contain still-valid implementation detail, that detail remains usable only if it conforms to v2.2.\n\nSee [`README.md`](README.md) for the documentation map and repository policy.\n"}