launch-checklistlisted

# Launch Checklist A checklist where every box can actually be checked: named owner, observable done condition, no ceremonial items. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Owner + verifiable done, every item:** each item carries a named owner role drawn from the stated context and a done condition someone can verify by looking ("macro IDs listed", "flag removed for cohort 1", "residency test passed on EU workspace"). "Align with X" and "make sure Y is ready" fail the gate. - **G2 — Context-tailored, context-bounded:** items derive from the stated context; owners are roles that exist in it. Generic-template items that contradict context (PR agency, app-store assets for a B2B web product) fail, as does inventing teams the input didn't mention. - **G3 — Rollback is an item:** the checklist contains rollback criteria with an owner and an observable trigger; unknown thresholds are labeled placeholders for the user to fill, never invented numbers. ## Steps 1. **Bank the context:** teams that exist (and their stated readiness), rollout mechanics (flag? cohorts?), regions and their constraints, pricing decisions, existing surfaces (docs, status page). This inventory bounds who can own anything. 2. **Walk the failure surfaces, not a template:** how does this launch break? Unprepared support, unwired billing, region compliance, missing rollback path, stale docs. Each stated context element that can fail becomes items; template items that m