product-launch-checklistlisted

# 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. ## Before you write **Run the input list below before you write anything. If one of those inputs is missing, ask for it and stop. Do not return a draft with a warning on it.** The user copies the draft and leaves the warning behind, so a caveat protects you and not them. **Ask at most THREE questions. Hard cap.** Before anything becomes a question, get it yourself: read `.agents/product-context.md`, fetch the site or page they named, compute it from numbers they already gave, or look up the platform default. Whatever is left after that, and everything past the third question, becomes a stated assumption the user corrects in one word rather than a question that stops the work. Number them, and s