# Launch Checklist

Launch is a product, operating, and support event—not only a deployment. Assign every item an owner and evidence link. Use **N/A + reason** rather than silently skipping an item.

[Kit README](README.md) · [Project Overview](Project%20Overview.md) · [PRD](Full%20PRD%20Template.md) · [Master Build Prompt](Master%20Build%20Prompt.md) · [Completion Checklist](Project%20Completion%20Checklist.md)

## Product and Content

- [ ] The value proposition, target user, MVP, and non-goals match the shipped behavior.
- [ ] A launch reviewer has evidence that the user can understand the offer within ten seconds.
- [ ] A launch reviewer has evidence that the user can reach any primary page in two navigation actions.
- [ ] A launch reviewer has evidence that the user can submit a contact request with clear confirmation.
- [ ] Onboarding, help, settings, empty states, errors, confirmations, and sample-data labels are complete.
- [ ] No placeholder, “coming soon,” fake integration, or unverified claim appears functional.
- [ ] Names, prices, dates, limits, policies, support details, and contact paths are accurate.

## Quality

- [ ] P0 automated and manual tests pass on supported environments.
- [ ] Accessibility, responsive/touch/keyboard, performance, reliability, and compatibility gates pass.
- [ ] Tests explicitly cover unclear positioning, oversized media, broken mobile navigation, forms that silently fail, missing page titles and alt text.
- [ ] Known issues have severity, workaround, owner, and review date.
- [ ] Backup, restore, migration, offline/sync, and rollback behavior are verified where applicable.

## Security and Privacy

- [ ] Authentication and object/role/tenant permissions are verified.
- [ ] Server-side contact validation is implemented and tested.
- [ ] Rate limiting and bot protection is implemented and tested.
- [ ] Safe HTML rendering is implemented and tested.
- [ ] Security headers is implemented and tested.
- [ ] Least-data analytics is implemented and tested.
- [ ] Secrets are absent from source, builds, logs, sample data, and documentation.
- [ ] Data collection, retention, export, deletion, consent, and incident ownership are documented.
- [ ] External dependencies and packages are approved, pinned, and monitored.

## Operations

- [ ] Production configuration, domains/app IDs, integrations, signing, certificates, and service limits are correct.
- [ ] Monitoring, alerts, dashboards, cost limits, logs, and escalation paths are active.
- [ ] Support owner, response expectations, FAQ/runbook, and user feedback channel are ready.
- [ ] Release owner, deployment window, staged rollout, smoke test, pause rule, and rollback authority are confirmed.
- [ ] The version, change summary, migration notes, and recovery steps are recorded.

## Growth and Learning

- [ ] contact completion rate: baseline [VALUE], launch target [VALUE], source [SYSTEM], owner [OWNER], first review [DATE].
- [ ] largest contentful paint: baseline [VALUE], launch target [VALUE], source [SYSTEM], owner [OWNER], first review [DATE].
- [ ] navigation success: baseline [VALUE], launch target [VALUE], source [SYSTEM], owner [OWNER], first review [DATE].
- [ ] organic landing-page visits: baseline [VALUE], launch target [VALUE], source [SYSTEM], owner [OWNER], first review [DATE].

## Go/No-Go Record

| Field | Decision |
| --- | --- |
| Candidate version | [VERSION/COMMIT] |
| Decision | [GO / CONDITIONAL GO / NO-GO] |
| Conditions | [CONDITIONS OR NONE] |
| Approved by | [OWNER(S)] |
| Evidence | [LINKS] |
| Rollback trigger | [THRESHOLD] |
| Next review | [DATE/TIME] |

Do not launch when a high-severity data, permission, payment, AI/tool, save, automation, or recovery risk remains unresolved.