Money blockers
Do not launch if checkout, webhook, paid unlock, receipt, refund/recreate, or support lookup is not proven.
- Webhook green.
- Receipt green.
- Paid unlock green.
Red door
Do not launch if
A hard blocker list: cases where ads, live payments, or broad traffic must not be enabled.
Sometimes the most profitable click is the Pause button.
Privacy blockers
Do not launch if private question, email, birth data, admin status, or support notes can enter public/OG/share/SEO layer.
- No private OG.
- No admin public leak.
- Deletion path clear.
Operational blockers
Do not launch if rollback, support inbox, issue log, recovery path, or owner availability is missing on launch day.
- Rollback known.
- Support ready.
- Owner available.
checklist
What to check
- No payment blocker.
- No privacy blocker.
- No delivery blocker.
- No mobile blocker.
- No legal boundary blocker.
- No rollback blocker.
red flags
When to stop
- Any blocker is marked as 'we will fix after launch'.
- Support recovery is manual but undocumented.
- Known broken mobile checkout is accepted.
- Public copy implies guaranteed future results.
done when
Definition of done
- Every hard blocker is resolved or launch is postponed.
- Go/no-go decision is written.
- Rollback and support are ready.
related doors
Final launch QAThe final check before opening the gates: data, money, email, SEO, legal, and support.Live payment drillThe minimal live/test Stripe drill: checkout, webhook, receipt, refund, and recovery.Data and privacy drillSupabase, RLS, storage, deletion, support access, and no-secret output.Legal reviewTerms, Privacy, Refund, Disclaimer, Florida/US risk.