Go-live readiness

Move from demo to controlled customer pilot with explicit acceptance gates.

Use this checklist before every customer pilot, executive demo, production deployment, or regional expansion review. Each gate has an owner, acceptance criteria, and evidence pointer.

Checklist complete3/6

remaining items require production validation

Critical pathAuth · DB · API

must pass before external customer traffic

Evidence modelOwner + URI

every gate carries a reviewable proof link

Launch modeControlled pilot

not unrestricted public traffic

Checklist

Acceptance gates.

Clean build

complete

Owner: Engineering

Fresh extraction builds without legacy route folders or versioned API leftovers.

Evidence: scripts/cleanup-legacy-routes.sh and docs/legacy-route-cleanup.md

Database migration

complete

Owner: Platform

Compatibility fixes, schema, RLS, and deterministic seed run without partial-state errors.

Evidence: docs/database-compatibility-fixes.sql, docs/supabase-schema.sql, docs/rls-policies.sql

Auth and tenancy

watch

Owner: Platform

Google/GitHub login, stale-cookie recovery, organization switching, and member role checks work on production domain.

Evidence: /login, /api/auth/clear?next=/login, /settings/organization

Telemetry security

watch

Owner: Infrastructure

Node telemetry requires a valid node key, updates last heartbeat, and creates critical incident records.

Evidence: /nodes/keys, /api/telemetry/ingest, docs/agent.md

Customer API gateway

watch

Owner: API

OpenAI-compatible routes respond and are ready for quota middleware and real runtime proxy.

Evidence: /gateway, /api/v1/models

Customer operations

complete

Owner: Customer Success

Customer accounts, risk register, support escalations, and go-live owners are visible for pilot reviews.

Evidence: /customer-success, /risk-register, /support, /go-live
Go-live Checklist | UmamiEdge