launch-reviewlisted

# Launch review A launch review is the last gate between a build and its users: a structured check that the thing is truly ready and that named people have said so on the record. It rots into theater when it becomes a rubber stamp, a meeting where everyone assumes someone else looked and no one holds the authority to stop the train. The whole point is to keep "no" a real and cheap option right up to launch. ## Method 1. **Drive the review from a written readiness checklist.** Functionality verified, error budget healthy, monitoring and alerts wired, rollback tested, legal and privacy cleared, support and docs ready, comms drafted. A checklist turns "are we ready" from a vibe into items that are each done or not. 2. **Give every checklist item a named owner who signs.** Not "engineering approves" but a specific person per area: the on-call lead for operability, privacy counsel for data, the support lead for readiness. A sign-off without a name is a gap nobody owns. 3. **Require the rollback and kill switch to be exercised, not just present.** The most common launch-day failure is a revert path that was written and never run. Demand evidence it worked in a realistic environment, with the time-to-revert measured and recorded. 4. **Name one launch owner who holds no-go authority.** A single person can halt the launch, and the room knows who it is before the meeting starts. Diffuse authority is how a known-broken launch ships, because stopping i