{"slug":"getting-started/README","title":"IntegrateWise Documentation","section":"getting-started","sectionLabel":"Getting Started","status":"unclassified","type":"document","path":"getting-started/README.mdx","bytes":6005,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Baseline:** 2026-08-11  \n**Authority routing:** [`CANON.md`](CANON.md)\n\nThe documentation tree contains current specifications, implementation references, commercial material, runbooks, generated mirrors and historical evidence. File names alone do not establish authority.\n\n## Start here\n\n1. [`CANON.md`](CANON.md) — authority order and disposition rules.\n2. [`architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md`](architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md) — single canonical architecture.\n3. [`architecture/ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md`](architecture/ONE_AUTH_HOST_CONTROLLED_PROJECTIONS.md) — host identity/connector authority.\n4. [`architecture/SHARED_FRONTEND_SHELL_AND_DOMAIN_OWNERSHIP.md`](architecture/SHARED_FRONTEND_SHELL_AND_DOMAIN_OWNERSHIP.md) — common Auth + Connectors + MCP + Platform across every frontend.\n5. [`architecture/LIFECYCLE_CONTINUITY_AND_PROJECTION_MAP.md`](architecture/LIFECYCLE_CONTINUITY_AND_PROJECTION_MAP.md) — phase/lifecycle/continuity-driven user flow and backend table → frontend projection map.\n6. [`architecture/PRODUCT_PACKAGE_RUNTIME.md`](architecture/PRODUCT_PACKAGE_RUNTIME.md) — Product Package contracts.\n7. [`architecture/EXECUTION_MODE_TOOL_CAPABILITIES.md`](architecture/EXECUTION_MODE_TOOL_CAPABILITIES.md) — Tool Capability Execution Mode.\n8. [`architecture/PLATFORM_MANAGEMENT_CONSOLE.md`](architecture/PLATFORM_MANAGEMENT_CONSOLE.md) — operator/admin console.\n9. [`operations/GO_LIVE_SEQUENCE.md`](operations/GO_LIVE_SEQUENCE.md) — release promotion and evidence gates.\n\n## Current product model\n\n```text\nHost identity + host connections\n→ One Auth\n→ connector projections\n→ Product Package\n→ Shared Frontend Runtime\n   Auth + Connectors + MCP + Platform\n→ frontend-owned lifecycle/domain projection\n→ Tool Capability\n→ Governance\n→ orchestrated execution\n→ reconciliation\n→ lifecycle transition + continuity update\n→ Spine / Business Context\n→ projection rehydrate\n```\n\nProduct Package:\n\n```text\nDiscovery + Capabilities + Spine Cache + ADK + Orchestrator\n+ Business Context + Loader + Normalizer + MCP Connector + Tool Capability\n```\n\nPlatform Backend:\n\n```text\nPackage Control Plane + Services + AI + Agents + Memory + Pipelines\n```\n\n## Frontend contract\n\nEvery frontend reuses:\n\n```text\nAuth + Connectors + MCP + Platform\n```\n\nEach frontend may independently own the rest: domain navigation, routes, lifecycle views, UX, local presentation state and domain-specific projection composition.\n\nEvery 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.\n\n## User/execution contract\n\n```text\nResume → Orient → Decide → Govern → Execute → Reconcile → Transition → Continue\n```\n\nExecution 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.\n\n## Documentation classes\n\n### Canonical\n\nOnly `architecture/INTEGRATEWISE_ARCHITECTURE_v2.2.md` defines the complete architecture.\n\n### Normative focused contracts\n\nThe 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.\n\n### Active implementation references\n\nFiles 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.\n\n### Historical / evidence\n\n`archive/`, `outbox/`, `internal/status/`, `architecture/source/` and files explicitly marked historical/superseded are lineage and evidence. They do not override current architecture.\n\n### Published mirror\n\n`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.\n\n## Core invariants for documentation\n\n- One Auth is the ecosystem entry.\n- Host connectors remain host-owned; IntegrateWise stores governed projections, not copied provider credentials.\n- Every frontend shares Auth + Connectors + MCP + Platform runtime capabilities.\n- Remaining domain/product frontend UX may be independently owned.\n- Frontend surfaces project backend canonical tables; they do not create page-shaped truth stores.\n- User flow and execution are lifecycle-, phase- and continuity-driven.\n- Twin is contextual and non-authoritative.\n- Business Context/Spine owns governed operational truth; Memory does not.\n- Tool Capabilities are first-class executable contracts.\n- Every execution passes Governance.\n- Governance returns `allowed`, `approval_required` or `blocked`.\n- Approved/executed outcomes are reconciled, captured as evidence/audit, and may drive validated lifecycle/continuity updates.\n- Platform configuration, activation, integration, discovery and schema flows are connector-aware.\n\n## Operations\n\nKey operational references:\n\n- [`operations/GO_LIVE_SEQUENCE.md`](operations/GO_LIVE_SEQUENCE.md)\n- [`operations/DEPLOYMENT_GUIDE.md`](operations/DEPLOYMENT_GUIDE.md)\n- [`runbooks/deployment-and-rollback.md`](runbooks/deployment-and-rollback.md)\n- [`runbooks/incident-response.md`](runbooks/incident-response.md)\n- [`runbooks/connector-oauth-troubleshooting.md`](runbooks/connector-oauth-troubleshooting.md)\n- [`playbooks/connector-go-live.md`](playbooks/connector-go-live.md)\n- [`playbooks/tenant-onboarding-and-initial-hydration.md`](playbooks/tenant-onboarding-and-initial-hydration.md)\n\n## Change rule\n\nWhen 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.\n"}