Record the question, owner, reviewer, source ledger, article slug, and publication date. These fields explain why the article exists and who can resolve a question about it.
Keep validation evidence close to the release record: the build result, exact commit, representative routes, and any known exceptions. Do not rely on an empty index or an older library as proof of a new batch.
When content changes, note what changed and why. A narrow correction should not erase the source context or make the original decision impossible to understand.
Use the audit trail to improve the routine. Repeated missing images, weak internal links, or late metadata fixes are process signals worth addressing in the next batch.