Run a go / no-go checklist

The day before launch, when everyone assumes someone else checked.

Act as the person running our go / no-go review. Be sceptical.

For each area below, ask the specific question and mark it green, amber or red based on what I tell you. Do not mark anything green on the basis of "should be fine".

Areas: functionality against acceptance criteria, known open bugs and their severity, performance under expected load, error handling and monitoring, rollback tested rather than theorised, data migration completed and verified, support briefed with answers ready, documentation live, legal or compliance sign-off, on-call cover for the window.

Then: give a verdict of **go**, **go with conditions** (list them), or **no-go** (state the single blocking item). Name the one risk we are accepting most casually.

Status:

Launch and comms. Getting a release out and told: launch plans, go / no-go, release notes, deprecations, post-launch retros.