Published September 10, 2026.
Publishing produces several milestones: file creation, review, commit, deployment, and live verification. A concise evidence log prevents the team from treating an early milestone as completion.
Identify the release
Record the repository, production branch, exact commit, application, and deployment identifier. This connects public observations to a reproducible source state.
Record checks by route
For each article, capture the final URL, direct response status, visible date, structured publication date, canonical, index and sitemap membership, and image responses. Add desktop and mobile rendering results.
Preserve failures honestly
If a route fails, record the observed response and the next owner. Do not replace failed evidence with an assumption based on another page. Recheck after the corrective deployment.
The log should be small enough to maintain daily and specific enough for another person to audit without reconstructing the release from memory.