Screenshots and chat messages are easy to lose. A release evidence record keeps the few facts needed to reproduce what happened without turning publishing into paperwork.
Record identities
Capture the repository, branch, immutable revision, deployment target, deployment identifier, and terminal result. Name the manifest that lists every intended route.
Keep preflight results
Store the build result, route-preservation diff, content counts, and any approved exceptions. Include enough detail to distinguish “not checked” from “checked and passed.”
Keep live results
For each new route, retain the direct status, canonical, visible and structured dates, family membership, sitemap membership, and hero or social image result. A summary count should link back to route-level evidence.
Set a retention owner
Choose where records live, how long they remain available, and who may amend them. Corrections should append context rather than erase the original observation. The archive then supports incident review and improves the next day's checklist.
