Corrections & Refinements — the visible trail¶
This page exists so that the accountability a byline normally supplies is supplied instead by a record anyone can inspect. EveryClaim carries no author's name (by design); in exchange, it owes readers something a named outlet is rarely asked for — a permanent, dated, public account of every time it was wrong in a way a reader could have seen. This is that account.
The commitment, in one line: corrections here are permanent and conspicuous. Nothing is silently edited away. When this site changes a published fact, the change is logged below with the date, what changed, and why.
The correction policy¶
What counts as what. We distinguish three things, because collapsing them is itself a way to hide errors:
- Correction — a factual error in published material: a wrong number, a wrong date, a misattributed source, an unsupported claim. Every correction is logged below.
- Refinement — a calibration or clarity change that does not reverse a fact: tightening a verdict, adding a caveat, sharpening a definition. Logged when it changes what a reader would take away.
- Update — new events or newly available evidence added to a living page. This is not an error; it is noted on the page itself with an as-of date, and is not logged here as a correction. (Ongoing-event figures always carry explicit dates for exactly this reason.)
Retraction. If a claim cannot be supported, it is struck — visibly, with a note explaining why — never quietly deleted. A removed claim leaves a mark.
How to report an error. If you find a claim that fails its tag — a source that does not say what we claim, a figure that is wrong, a dispute we have miscalibrated — report it through Suggest a Topic. Substantive challenges receive a response, and where the challenge is right, a logged correction. Finding an error here is a contribution to the project, not an attack on it.
What this log does and does not include. Most errors in a project built this way are caught before publication, during the source-audit and verification passes that precede every document — for example, the "Muslim Brotherhood black-list count" was corrected in research before the terror-finance document was written, and the Journal of Palestine Studies' own correction to the "160 children died digging tunnels" figure was incorporated in drafting, so neither ever reached a reader. This log is deliberately not for those. It is for the other kind: errors that were live, that a reader could have seen, and that were changed afterward. Padding a corrections log with pre-publication catches would defeat the only purpose it has.
The log — post-publication corrections¶
Most recent first. Each entry is tagged by type.
2026-08-13 · [TOOL] · Check-a-Claim returned inconsistent, under-calibrated verdicts on "apartheid" questions¶
The live claim-checker returned "partially true" for "Is Israel an apartheid state?" without engaging Israel's documented record of Arab-citizen political rights — and returned a different verdict for the same question about Lebanon depending only on how it was phrased. Two fixes followed: a new page applying the 1973 Apartheid Convention's legal elements to every state in the region at one standard, and a new engine rule requiring legal-category claims (apartheid, genocide, and the like) to be graded by their definitional elements rather than freelanced. The whole-state claim now returns "contradicted," with the citizen record stated in the answer. The correction cut in two directions at once: against an anti-Israel over-claim, and against the tool's own inconsistency.
2026-08-11 · [CONSISTENCY] · Five documents published without the standard summary box¶
Documents 32 through 36 went live missing the plain-language "Short Version" summary that every other document carries — a defect a reader comparing two pages would see immediately. The summaries were written and added to all five. The gap came from a document template that had not been updated as the collection grew; the template was fixed so it cannot recur.
2026-08-08 to 2026-08-10 · [TOOL] · Check-a-Claim gave imprecise verdicts on comparative and measure-dependent claims¶
The live engine graded claims such as "malnutrition is worst in Gaza" as a vague "partially true" instead of performing the comparison the word "worst" demands. After stress-testing exposed the pattern, rules were added requiring the engine to extract and rank the comparable figures before ruling, to name which measure a verdict depends on, and to treat percentages and absolute counts as different rankings. Retested against the same claims, the engine now ranks the figures and rules accordingly.
2026-08-02 · [PRIVACY] · The project owner's name appeared on live pages¶
A user-experience review found the project owner's full name present on several live pages, as residue from internal working files. Because the project's design is deliberate anonymity (About), the name was removed the same day it was found, and a full sweep followed to remove it and other internal identifiers across the site. This entry is here because a correction record that hides its most awkward item is worth nothing.
Before first publication — the pre-launch hardening¶
These did not reach readers, and so are not "corrections" in the sense above. They are recorded here so the scale of the process behind the site is visible, not to inflate the count.
- The claim-by-claim audit (July–early August 2026). Before the site went public, the corpus was audited against its sources. The audit flagged roughly 390 problems across about 1,760 tagged claims — including about 25 fabricated or misquoted sources (some of them AI-generated citations in the project's own drafts) and about 65 factual errors. Every one was corrected against real sources, rewritten to what the evidence supports, or removed, before publication.
- The adversarial red-team review. A separate hostile review of the near-final site produced twelve high-severity findings — an inaccurate quotation, instances of one-sided labeling, an anachronism, among others — all corrected before wide release.
The detailed pre-launch correction logs live in the project's source repository.
The standing rule¶
From here forward, every post-publication correction is logged on this page — dated, with what changed and why — and no published fact on this site is ever changed silently. That is the deal this project offers in place of a name: you cannot check who wrote it, but you can check everything it ever got wrong.
See also: How We Verify · Verification Standards · Sources & Links · About