A short alias could match inside another outlet’s name. Matching was changed to whole tokens and verified domains.
Corrections policy and log
Errors are corrected visibly, proportionately and traceably. A correction is not hidden inside a silent update when it affects the conclusion.
How to request a correction
Send the exact URL, the disputed statement, a source that contradicts it and a short explanation through the contact page. Unsupported opinions can be considered but do not require a factual change.
Correction levels
| Level | Example | Response |
|---|---|---|
| Minor | Typo, broken link or formatting. | Direct fix and review date. |
| Material | Figure, attribution or context changing interpretation. | Visible note on the page and entry in this log. |
| Critical | Open/closed status supported by invalid evidence. | Immediate downgrade, new run, automated test and public explanation. |
Initial log
A headline containing “open” could be read as proof even when it asked a question. Questions and analytical headlines were excluded from operational confirmation.
Revalidation was strengthened so an old invalid confirmation could not preserve a certainty state.
What is not erased
Status history and technical commits are retained so the evolution can be reconstructed. When a historical entry contains an error, the correction is documented and the item is prevented from acting as a current confirmation.