Quiet launch
First open production without ads: check home, login, search, pricing, trust, Tarot flow, and account.
- Home opens.
- Account opens.
- Search works.
- Tarot path starts.
Gate opening day
Go-live day
Launch day order: quiet deploy, smoke test, test payment, first real users, support, and error diary.
Launch should be a ceremony with protocol, not a blind jump into a portal.
Test purchase
Before real users, run the paid path again in test mode or a minimal live scenario under control.
- Webhook live/test matches mode.
- Receipt arrives.
- AI answer ready.
First users
First users should arrive in a small group. Stay near logs, email, and Stripe dashboard that day.
- Support email open.
- Runtime logs open.
- Stripe dashboard open.
- Issue log is maintained.
checklist
What to check
- Do not run mass ads before first live smoke test.
- Keep known-good rollback ready.
- Record all issues in launch diary.
- Check support response templates.
- After 24 hours, review payments, errors, and user behavior.
red flags
When to stop
- Many users arrive before recovery is checked.
- Support email is not ready.
- No rollback version.
- Ads are on before live paid smoke test.
done when
Definition of done
- First day passed without critical privacy/payment errors.
- All support requests logged.
- There is a fix plan for the second iteration.
related doors
Production checklistThe master list before real users enter.Stripe test flowCheckout, webhook, paid status, AI, receipt, and access.MonitoringStripe, OpenAI, Supabase, email, cost spikes, and alerts.Rollback planWhat to do if something breaks after deploy.SupportLost links, payments, accessibility, and errors.