Corrections Policy
The log is a record. Records that quietly shapeshift are not records.
Append-only
When a published entry is wrong, or incomplete in a way that would mislead, the desk adds a correction. It does not silently rewrite the published claim and hope nobody notices.
A correction includes:
- what was wrong (quoted, not paraphrased into softness);
- what is now understood, with sources;
- the date of the correction;
- a stable identifier, referenced from the entry’s
correctionsfront matter.
The original wording remains readable. If the error was in a headline, the old headline is preserved in the correction note.
Git history
This repository’s history is part of the public trail. Do not force-push over a published entry to hide an error. Do not strip a broken paragraph from the file and pretend it never ran. Later editors should be able to see what readers saw.
The repository’s docs/corrections.md is the operator checklist. It is not a second public log.
Where corrections appear
A correction banner renders at the top of the affected entry. Index pages that still list the entry should not pretend the error did not happen if the error changed the meaning of the list item.
What is not a correction
Tightening a sentence that did not change the facts is an edit, noted in updatedAt, not a confession. Adding a later official response is an append, and is handled under Right of Reply. Retracting an entry (status: retracted) is for cases where the entry as a whole should not have run; the file remains, marked.
How to send one
Until monitored intake is live, see Contact and Right of Reply. Do not assume an unmonitored form was read.