Published September 7, 2026.
When publishing evidence is scattered across chat, commits, and dashboards, small defects become hard to diagnose. A one-page manifest creates a shared chain of custody.
Record identity before merge
List each route, family, title, publication date, canonical target, and image path. Add the repository, branch, and intended application. This catches a wrong slug or deployment target before it becomes public.
Attach the release state
After pushing, record the full commit SHA and deployment identifier. Do not treat a successful Git push as proof that production changed. Wait for the matched application to reach a terminal successful state.
Close every live gate
For each route, verify HTTP status, visible date, structured publication date, self-canonical, family index membership, sitemap membership, and image responses. Note the time and hostname used.
The manifest is evidence, not ceremony. If any route fails, leave the batch open with a named owner and exact repair rather than summarizing the release as mostly complete.