---
name: release-verify
description: A release is done only when the live URL passes an end-to-end check, with a rollback ready.
---

# Release = verified live

1. Before deploying, note the current production version so you can roll back in one command.
2. After deploying, run the real user path against the live URL (not localhost): load the page, call the API, complete the main action, and check the result is stored/visible.
3. Check content, not just status codes: an empty article with a 200 is a failure.
4. If any check fails, roll back first, then debug.
5. Report at check-in: `releases.shipped` and `releases.verified_live`, with the URLs you checked in `evidence_urls`.