Public resource · transparent corrections
Change-log method: how to document a correction without rewriting history
A trustworthy change log shows what changed, why it changed, and when—not just that a page has a newer date.
Record the change itself
A useful correction entry includes the date, affected page, the material statement or record that changed, the reason, and a concise description of the update. It should not rely on vague phrases such as ‘improved accuracy’ when a factual point was altered.
This allows readers to understand whether the edit was a citation update, a terminology correction, a structural change, or a clarified evidence limit.
Do not confuse a page update with a verification event
An editorial edit and a cart-code check are different events. A page can receive a correction without a new code verification, and a documented cart event can occur without changing the research library. Their dates should remain separate.
This distinction prevents a general ‘updated today’ stamp from misleading readers about what actually happened on that date.
Preserve history with context
When past records are incomplete, label them as legacy context rather than upgrading them retroactively. Future entries can use a higher evidence standard without erasing the site’s timeline.
This method supports auditability and discourages hidden revision practices.
Separate a correction from a new version
Not every edit has the same significance. Typographic repairs, navigation improvements, and expanded explanations can be grouped as editorial maintenance. A changed source, a corrected factual statement, or a revised verification boundary should be called out as a material update because it changes what a reader can reasonably infer.
A disciplined log also records whether an earlier statement was removed, narrowed, or replaced. That detail matters when a reader is comparing an archived claim with a current page and helps prevent a date field from standing in for the substance of the update.
A log entry should be understandable without the editor’s memory
Months after an edit, a reader should not need to guess why a page changed. A material log entry therefore benefits from a clear before-and-after description, the affected route, the date, the source or event that prompted the update, and the status of related pages. This makes the change record useful to an outside reviewer instead of turning it into a private note that only the original writer can decode.
The method also requires restraint. A correction does not need to dramatize a minor wording edit, and routine maintenance should not be used to imply a new evidence event. By matching the entry’s detail to the significance of the change, the log preserves both accuracy and proportion while keeping the historic record intact.