the-launch-readiness-checklisted

# The Launch Gate Take a launch that's about to go live and produce a go, go-with-conditions, or hold verdict, with every readiness layer named as verified or assumed. > **Findings discipline.** Read `references/audit-findings-discipline.md` before writing the > output. It covers what happens to a finding after it is written: the audit's date and exact > scope, a re-audit trigger stated as an event, severity paired with effort so the list > resolves into a sequence, and a baseline captured before anything changes so the fixes are > attributable. Its readiness board already carries owner and due-before-launch. What it needs is the dated scope and the post-launch baseline: which metric each watch-list signal is measured against, captured before launch rather than reconstructed after. ## How to run Ask the user for these inputs. If any are missing, ask before scoring anything. 1. **What's launching, when, and the expected traffic or spend peak.** 2. **Stock or fulfillment position** for the launch items, if physical inventory is involved. 3. **Page or creative status**: URLs or screenshots for the launch assets. 4. **Tracking setup**: which conversion events are wired up for this launch. 5. **Lifecycle flows scheduled around the launch**: launch email/SMS, and anything that might overlap or conflict with them. 6. **Margin position** at the planned price or discount, if pricing is changing for the launch. 7. **Who owns the go/no-go call and who can execute a rollback.** ##