{"slug":"canonical/16-ONBOARDING-CUSTOMER-ZERO-AND-GO-LIVE","title":"16 — Onboarding, Customer Zero and Go-Live","section":"canonical","sectionLabel":"Canon","status":"canon","type":"document","path":"canonical/16-ONBOARDING-CUSTOMER-ZERO-AND-GO-LIVE.md","bytes":1842,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Canonical reference:** `00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` §24, §27  \n**Status:** Canonical\n\n---\n\n## 1. Onboarding\n\nOnboarding does not hand the user an empty workspace to configure manually. Onboarding creates a Spine Context, hydrates the Spine and then computes useful projections.\n\n```text\nIdentity\n→ Organization / Role / Responsibility\n→ Goals and Operating Context\n→ Connect Reality\n→ Discovery\n→ Configuration\n→ Activation\n→ Initial Hydration\n→ Business Context Spine\n→ Personal Contextual Memory Initialization\n→ AI Continuity / Twin Activation\n→ Capability Activation\n→ Projection\n→ SpineWorkspace\n```\n\nThe first useful experience should already contain real context from connected systems, clear coverage/readiness state, relevant Work and a functioning Twin.\n\n## 2. Customer Zero\n\nIntegrateWise must operate IntegrateWise itself. Customer Zero is the first real tenant, not a demo architecture.\n\nCustomer Zero should preserve the operating history of the company: product, architecture, code, decisions, tasks, funding/GTM work, connectors, documents, incidents, releases, AI sessions, agent work, approvals and outcomes.\n\n## 3. Minimum end-to-end launch proof\n\n```text\nOne Auth\n→ controlled connectors\n→ Initial Hydration / Flow A-B-C-D\n→ valid Base Spine\n→ Human Workbench projection\n→ AI Workbench/Twin context\n→ proposal\n→ Governance approval or bounded policy allow\n→ Capability Fabric route\n→ Hermes execution\n→ provider outcome\n→ re-ingestion\n→ verification and reconciliation\n→ visible Human + AI Workbench rehydration\n```\n\nUntil this loop is demonstrated with telemetry, rollback, security and operational support, the release classification should remain Customer Zero / controlled beta rather than broad GA.\n"}