Corrections
Last updated: May 16, 2026
When a published brief is materially wrong, the correction is recorded here with the date, severity class, affected URL, and a one-sentence summary of what changed. Briefs are not silently deleted: a retracted brief continues to resolve at its original URL with the retraction notice in place.
Severity classes
| Class | Examples | Where it appears |
|---|---|---|
| Minor | Typo, formatting glitch, misspelled persona name, outlet attribution off by one | Silent fix on the brief. Logged here only if reader-facing. |
| Material | A factual claim is wrong, a citation does not support the claim, a quote is misattributed | Dated inline notice on the affected brief plus an entry below. |
| Substantive | A threat-level call, vote prediction, or analytical assessment is wrong in a way that would mislead a reader's decision | Prominent inline retraction on the brief, entry below, and a callout in the next day's RSS / JSON feed. |
Public log
No corrections have been issued. The log is empty.
How to issue a correction request
Submit a correction through our contact form with:
- The URL of the affected brief (e.g.
/desk/intel/2026-05-16) - The specific passage you believe is wrong
- The source you would point to instead
- Whether you would like a public acknowledgement that you raised it (we default to no)
We aim to acknowledge correction requests within 48 hours and resolve them within five business days. Substantive corrections receive a prominent inline retraction within 24 hours of confirmation.
Related policies
- Ethics policy — full correction-and-retraction protocol
- Methodology — how a brief is built in the first place
- Track Record — per-day calibration scoreboard (HIT / PARTIAL / MISS / NULL_COVERAGE)
- Fair use & takedowns — DMCA contact