Corrections

We are wrong in public, on this page, with receipts.

How corrections work

• Email hello@ctsignal.org with the story URL. Any factual error — wrong question matched, wrong framing, stale data presented as new — is a correction.
• The story page is annotated and re-published; the original card JSON stays in the archive and commit history, so the correction is diffable like code — because it is.
• If a whole indicator class proves unreliable, we retire it from the catalog and say so here, not quietly.

How this differs from a normal newsroom

Most errors here are mechanical (an upstream dataset revised, an endpoint changed shape), so most fixes are automatic on the next fetch. What we list below are the ones where a reader saw something we'd have kept serving.

Corrections to date

None yet. That is a small sample, not a claim of perfection — our failure log is public and longer than our corrections list on purpose: failures that stop a card from publishing never needed correcting.