16 — Onboarding, Customer Zero and Go-Live

Canonical reference: 00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md §24, §27
Status: Canonical

---

1. Onboarding

Onboarding does not hand the user an empty workspace to configure manually. Onboarding creates a Spine Context, hydrates the Spine and then computes useful projections.

Identity
→ Organization / Role / Responsibility
→ Goals and Operating Context
→ Connect Reality
→ Discovery
→ Configuration
→ Activation
→ Initial Hydration
→ Business Context Spine
→ Personal Contextual Memory Initialization
→ AI Continuity / Twin Activation
→ Capability Activation
→ Projection
→ SpineWorkspace

The first useful experience should already contain real context from connected systems, clear coverage/readiness state, relevant Work and a functioning Twin.

2. Customer Zero

IntegrateWise must operate IntegrateWise itself. Customer Zero is the first real tenant, not a demo architecture.

Customer 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.

3. Minimum end-to-end launch proof

One Auth
→ controlled connectors
→ Initial Hydration / Flow A-B-C-D
→ valid Base Spine
→ Human Workbench projection
→ AI Workbench/Twin context
→ proposal
→ Governance approval or bounded policy allow
→ Capability Fabric route
→ Hermes execution
→ provider outcome
→ re-ingestion
→ verification and reconciliation
→ visible Human + AI Workbench rehydration

Until this loop is demonstrated with telemetry, rollback, security and operational support, the release classification should remain Customer Zero / controlled beta rather than broad GA.