Method · Honesty Box
How we publish corrections and retractions.
The retraction protocol every Kepie Watch claim is governed by.
The audit log behind every number
At render time, every public number on Kepie Watch is written into a private audit table — the SQL that produced it, the sources cited, and the value shown. The audit log is append-only. When a correction needs to be published, the original audit row stays exactly as it was; a new field on the same row records the corrected value, the reason, and the date.
What happens when a number is wrong
- We update the audit row with the corrected value + the reason — never by editing or deleting the original entry.
- The page that carried the original number gets a red correction notice banner above the place where the number lives. The original number stays visible on the page, with a strike-through where appropriate — readers who arrive via an old link see exactly what they were promised, plus what changed.
- The Honesty Box page lists the correction with a link straight back to the corrected page.
- The next email digest opens with the correction. Subscribers see it before anything else.
What we never do
We never silently edit a published number. We never delete a wrong claim from history. We never re-time a correction to make it look fresher than it was. A correction in the audit log carries its true publish-date and its true correction-date, and the gap between the two is on the public record.
How to flag a number
Email press@kepie.app with the page URL and the number you’re questioning. We’ll re-run the producing SQL against the live data, share the result back, and if there’s a discrepancy, the correction goes up the same day.