Every error, dated, with the original claim still visible.
Standing rule: no scores. Color marks whether something is in force, reversed, contested, concluded, or permanent, not good or bad.
Unscored · 97 entries · last change 2026-08-16
New here? Read this first (30 seconds)
Color is a legal fact, not an opinion. It shows (whether something is still in force, was reversed, or is contested in court), never whether it was good or bad.
Every number links to its source and to how strongly it can be tied to the action (). Click any figure to see the full evidence.
Nothing here is scored, graded, or ranked. When two credible sources disagree, this archive shows both numbers instead of picking one.
Wins are in here too. See or filter the Ledger by .
Nobody is asking you to trust a byline. There isn’t one — the archive is anonymous, on purpose, which is exactly why it has to be checkable without one. See and check one entry against its own source yourself.
Corrections ledger
Every substantive change to a published claim appears here with the original text intact. Nothing is edited silently: not a figure, not an attribution level, not a status. A reference site that quietly revises itself is indistinguishable from one that was never careful.
The point is not that this archive is error-free. It will not be. The point is that its errors are visible, dated, and attributable, so a reader can judge how often it is wrong and in which direction.
Error rate, published
Corrections logged
39
Material: changed a claim
18
Reader-submitted
11
Self-found: not reader-submitted
28
Publish this count whether it flatters the project or not. A tracker claiming zero corrections after a year of publication is either not being read or not being honest.
Published as
statusDetail described the sentence only as "An unconditional discharge imposes no imprisonment, fine, or probation but leaves the conviction in place," without Judge Merchan's own stated reason for structuring it that way. Read on its own, the line can land as "the crime didn't really matter," which is not what the record supports. Merchan said the opposite.
Corrected to
Added one sourced sentence, in Merchan's own words from his January 10, 2025 sentencing statement: the discharge protected "the office of the president... not the occupant of the office," and the presidential protections "do not reduce the seriousness of the crime or justify its commission in any way", an accommodation of the incoming presidency and pending appeal, not a finding about the conduct underlying the 34 counts. Added a dedicated Tier 2 source for the sentencing statement itself (CBS News), distinct from the general case-record link already in the entry's sources.
How the error happened
The entry said the sentence carried no penalty but didn't say why the judge structured it that way. He was explicit it was to protect the presidency, not a judgment that the crime didn't matter. Added his own words so readers get the actual reasoning instead of drawing the wrong conclusion from a bare fact.
Full technical detail
Craft-fixable (invariant 9, Bin A): the conviction, the 34 counts, and the discharge itself were never in dispute, only whether the entry's own explanation of the sentence gave the reader Merchan's actual rationale, or let "no penalty" imply the offense wasn't serious. Logged per invariant 8: changes are recorded whether or not they are substantive.
2026-08-16 · Corrections log: wording aligned with the Masthead's own review-record disclaimerEditorial: no factual change
Published as
Ten Corrections entries (dated 2026-08-14 and 2026-08-15) described the findings behind them as coming from an "independent fairness review," "independent readability review," or "a reviewer built specifically to distrust euphemism and false balance", while the Masthead's own "Review record" section states plainly, describing the same underlying passes: "These passes were run by the author against the author's own work... This is not independent review." A reader who opened Corrections without first reading that Masthead disclaimer would reasonably take "independent" at face value, which contradicts what the archive says about itself two clicks away.
Corrected to
All ten occurrences reworded to match the Masthead's own framing: "independent fairness review" and "independent readability review" became "self-run fairness-panel pass" and "self-run readability pass"; "Raised independently by two readers" and "flagged independently by reviewers" became "Raised by two readers... in a self-run fairness panel" and "flagged by personas... in a self-run fairness panel"; and the "reviewer built specifically to distrust euphemism and false balance" line now reads "one persona in a self-run fairness panel, built specifically to distrust euphemism and false balance." No finding, fix, source, or fact described in any of the ten entries changed, only the words describing who ran the review. The Masthead's own disclaimer (`MastheadClient.tsx`, "This is not independent review") gained one added sentence making explicit that the same applies to every fairness-panel or readability-pass reference elsewhere on the site, including here in Corrections, so the disclaimer's scope isn't limited to a reader who happens to visit Masthead first.
How the error happened
Corrections kept calling these self-run review passes "independent," while the Masthead page says outright that nothing on the site is independent review because the author reviews the author's own work. That's a real inconsistency a careful reader would catch, so the wording in Corrections was changed to match what the Masthead already says, no finding or fix described in any of the ten entries changed, only who gets credited with running the review.
Full technical detail
Invariant-9 Bin A: a craft-fixable presentation/consistency gap, not a truth-immutable one. Nothing about what was found or fixed was ever in dispute, only whether it was accurate to call a review the author ran on the author's own work "independent." It was not, by the Masthead's own words, and the two pages now agree. Logged per invariant 8: changes are recorded whether or not they are substantive.
2026-08-16 · Financial ties: withheld new-entrant disclosures row gets a second, independent source and a corrected tierMaterial: source added, tier corrected, no fact changed
Published as
The "withheld-new-entrant-278" row (the archive's own "most careful page, on purpose") rested on a single source: a June 2025 letter from Sen. Adam Schiff, a Democratic critic of the administration, labeled "Tier 2" even though this archive's own glossary defines Tier 2 as peer-reviewed research or a nonpartisan institution, and its own precedent (a bipartisan Khanna/Massie legislator letter elsewhere in the archive) classifies a lawmaker's letter as advocacy, not Tier 2. That made this the one row on the archive's most sensitive page thinner than the sourcing bar the rest of the site holds itself to. checkEntry()'s advocacy-not-alone rule requires a Tier 3 source never stand alone, but financialTies.json sits outside checkEntry()'s coverage entirely, since it only walks entries.json.
Corrected to
Added a second, independent citation: NOTUS (the Allbritton Journalism Institute's nonpartisan nonprofit newsroom), "The White House's Financial Disclosures for Top Officials Are Incomplete" (Mar. 10, 2026), its own comparison of OGE's public disclosure database against the White House's posted disclosures, finding several senior officials, named, still missing or incomplete months after the statutory deadline, plus an on-the-record White House response ("nothing is being withheld"). The Schiff letter's tier is corrected from "Tier 2" to "Tier 3" to match the archive's own definition and precedent; it remains cited, now alongside the independent source rather than alone. The underlying fact (that new-entrant disclosures were not made public on schedule) is unchanged and now doubly sourced.
How the error happened
Fairness-review finding: a single-opposition-senator source on the archive's most sensitive page is thinner than this archive's own stated sourcing discipline. Bin A (invariant 9), craft-fixable by adding an independent source and correcting a tier label, no assertion about the underlying fact changed. financialTiesData.test.ts now carries a hand-written mirror of checkEntry()'s advocacy-not-alone rule so this dataset isn't structurally exempt from it going forward.
Published as
The "Southern border apprehensions fell sharply" claim already carried three estimates (the 85,218/92%-decline figure via FactCheck.org, the administration's own framing of it as its central achievement, and a negative-finding estimate on the absence of a causal-attribution study). A fairness review flagged that this claim reads thinner than the same entry's enforcement-cost claims (majority non-criminal arrests, four deadly task-force shootings with two named victims, sustained protest), which run longer and carry more specific detail. That review's premise that this claim was "a single bare statistic beside a one-line DHS quote" was itself inaccurate (it already had three sourced estimates) but the underlying observation, that the claim lacked absolute/comparative magnitude next to a headline percentage, held.
Corrected to
Added a fourth estimate, sourced to Pew Research Center's analysis of CBP data (published Feb. 2, 2026): Border Patrol recorded 237,538 southwest border encounters in FY2025, the lowest of any fiscal year since 1970, with monthly encounters falling below 10,000 starting February 2025, down from 46,609-56,515 a month in the outgoing administration's final quarter (Oct.-Dec. 2024). This gives the 92% figure the same kind of magnitude/comparative texture the enforcement-cost claims already carry, without inventing narrative or named individuals to force a symmetry the two claims don't share in kind (an aggregate statistic versus named people who died).
How the error happened
Fairness-review finding, invariant-9 Bin A (craft-fixable: additional sourced texture, not a truth change). No existing fact, figure, or estimate was altered or removed.
Published as
The summary read "A US-brokered framework produced a ceasefire in Gaza and the release of remaining living hostages, after two years of war." That was stated as flat archive fact, with none of the hedge this same entry already carries two fields down: its own "contested" field states "Credit for a mediated agreement is inherently shared among mediators and parties. This entry records the US role as decisive per analysts, not as sole cause," and its own effect estimate attributes the identical claim to a source ("US pressure on both parties is widely credited by regional analysts as decisive in reaching the framework"). The summary is the first and most-read text on the entry and asserted the stronger, unattributed version of a claim the entry's own body explicitly disclaims, a matter of characterization (credit-sharing among multiple mediators, Qatar, Egypt and Turkey, and both parties to the war), not settled fact. `checkEntry()`'s CAUSAL check only scans `effect.claim`, so nothing mechanical catches an inconsistency between an entry's summary and its own body.
Corrected to
Summary now reads "A ceasefire in Gaza and the release of remaining living hostages followed a US-brokered framework, after two years of war." The ceasefire and release are stated as fact (they are); the US framework's role is stated as sequence ("followed"), not asserted causation, matching the hedge already written into this entry's contested field and its own sourced estimate. No fact changed: the hostage release, the framework, and the timing are all still stated plainly.
How the error happened
The summary is the archive's own text, unattributed, and is read by far more people than the effects/contested fields beneath it. It should never assert a stronger claim than the entry's own sourcing supports two fields down. Logged per invariant 8: corrections are logged whether or not the underlying fact changes, and this changes published prose.
2026-08-16 · Financial ties: new row: Musk's SpaceX/Tesla/xAI federal ties and DOGE's reach into their regulatorsAdditive: new sourced row, no existing claim changed
Published as
The Financial Ties view documented Trump's own holdings and the Trump-family crypto/federal-crypto-policy overlap, but carried nothing on Elon Musk (named in the DOGE entry as its public face) despite SpaceX and Tesla holding federal contract and regulatory relationships with agencies (FAA, NHTSA) that DOGE's government-wide reach touched.
Corrected to
Added a documented_adjacency row: SpaceX's cumulative federal contract total (more than $26 billion, USASpending.gov, pulled live from the API on 2026-08-16, not estimated), Tesla's comparatively small direct contracts and xAI's 2025 GSA Grok agreement, alongside the documented fact that DOGE (which Musk led as a Special Government Employee) had government-wide agency reach that included the FAA (which licenses SpaceX launches) and NHTSA (which regulates Tesla vehicle safety, with open investigations into its autonomous-driving systems during the same period). States the adjacency only; no motive asserted, matching the treatment already given to the Trump-family crypto row (wlf-crypto-overlap). Links to the existing "doge" entry via both entryId and intersects, the same one-directional linking every other financial tie already uses. No prose was added to the DOGE dossier itself.
How the error happened
Same class of gap as the crypto-overlap row this archive already carries: a documented financial interest sitting next to a documented official action, in the same person's official role. Sourced to USASpending.gov's own recipient-profile data, retrieved and read before the row was written, per this dataset's rule that a row exists only once its underlying document has been pulled.
Published as
The fake-elector effect claim ("Certificates from fake electors were submitted in seven contested states") documented the scheme as established fact (the House Select Committee's report, Eastman's upheld disbarment, and state grand jury indictments) but carried no estimate stating the electors' own defense theory, that the slates were 'contingent,' meant to preserve litigation options pending court challenges. Every other comparably contested entry in this archive (DACA, sanctuary jurisdictions, DEI, the transgender military ban, Title X) pairs a disputed finding with the accused party's own characterization as a labeled estimate; this was the one exception.
Corrected to
Added a fourth estimate to that claim: Georgia electors Shafer, Still, and Latham's 'contingent' defense theory, which they pressed in a bid to remove their state prosecution to federal court (a bid the Eleventh Circuit rejected in October 2024 (No. 23-13360) on jurisdictional grounds, without ruling on the theory itself) and the same contingent-purpose argument Michigan defendants raised, where the presiding judge dismissed all 15 remaining charges in September 2025 citing insufficient evidence of intent to defraud. Labeled `lean: "Defense position"`, matching this archive's existing classifier and the same badge already used on the DACA and transgender-military-ban entries. The Eleventh Circuit opinion (Tier 1, read directly and confirmed to contain the 'contingent' theory and the removal ruling) and reporting on the Michigan bench ruling (Tier 2: the Michigan court issued no written order, only an oral ruling from the bench, so it is sourced to contemporaneous reporting rather than a document that doesn't exist) were added to the entry's sources.
How the error happened
Flagged by a fairness review as this entry's one departure from the archive's own established, code-enforced convention for contested claims. And the review named it as the entry this readership will scrutinize hardest. The existing Direct-attribution finding and its three estimates (HSC report, upheld disbarment, grand jury indictments) are untouched; nothing about the scheme's documentation changed. This only adds the accused parties' own account, sourced to the actual filings and rulings, the same way the archive already treats every sibling contested entry.
2026-08-16 · Overview: new staple: Cabinet turnoverAdditive: new sourced figure, no existing claim changed
Published as
The "Standing indicators" strip on Overview had no figure for Cabinet-level appointments or turnover, despite tracking judges seated, border enforcement, and other personnel-adjacent figures.
Corrected to
Added "Cabinet turnover: 4" with a sub-line naming which departments changed hands and which replacement is still pending confirmation. Sourced from this archive's own `confirmations.json` (built from senate.gov roll-call XML via `npm run data:confirmations`, re-run this session to confirm it was current) cross-checked against Brookings' Cabinet turnover tracker and Wikipedia's dismissals/resignations list: 20 secretaries confirmed Jan-Mar 2025; Homeland Security (Noem, fired), Attorney General (Bondi, fired), and Director of National Intelligence (Gabbard, resigned) already have Senate-confirmed replacements on record (Mullin, Blanche, Clayton); Labor (Chavez-DeRemer, resigned) has a nominee (Sonderling) not yet confirmed as of the most recent reporting found.
How the error happened
User request. Brookings' own tracker counts only 3 turnovers as of Aug 11, 2026 because its methodology does not appear to treat Director of National Intelligence as Cabinet rank, while this archive's confirmations dataset (and the administration's own practice) does; both are real, differently-scoped counts rather than one right and one wrong. Went with the archive's own primary-sourced dataset (4) and named the discrepancy here rather than silently picking whichever number was easiest.
2026-08-16 · Masthead: live integrity audit: target-size row corrected from stale to currentEditorial: corrected stale status text on the archive's own audit page, no entry content changed
Published as
The "Controls below the WCAG AA/AAA target-size minimum" row read "Not yet re-measured against the built app". No longer true. It had in fact been measured twice: a desktop pass (0 violations, CI-enforced) and a separate manual mobile pass at 390px (also 0 violations), neither reflected in the copy.
Corrected to
Row now states both real results and the honest remaining gap: 0 violations at each size, desktop enforced in CI, mobile verified by hand but not yet wired into CI, which is why the row still reads "warn" rather than "pass."
How the error happened
User asked for the Masthead's integrity-audit numbers to be checked and brought current. Every other figure in that section (`auditSummary()` and the full `checks` table) already computes live from `ENTRIES` on every render; this one row was the sole hardcoded exception and had gone stale relative to work already documented in CLAUDE.md.
2026-08-15 · Site-wide: pre-publish sweep: 5 real defects found and fixed across Indicators, Markets, Personnel, Dossiers, and the shared onboarding bannerMaterial: one recurring invariant-7 violation across 3 views, plus a broken mobile control and a non-clickable citation
Published as
Indicators' and Markets' term-comparison tables, and Personnel's yea/nay vote bars, colored figures using the site's actual `--color-cost`/`--color-benefit` tokens purely by arithmetic sign or vote direction, a falling unemployment rate or a `nay` vote rendered in the same red used elsewhere for net-cost incidence, silently contradicting "color marks standing only, not good or bad" on pages that state that exact rule. Separately, the shared "New here?" onboarding banner's dismiss button landed at the bottom-left of the card instead of pinned near the heading whenever its text wrapped on a narrow screen (a flex-wrap/justify-between interaction), and every view's specific explanatory subtitle was deleted from the DOM entirely on mobile (`hidden md:block`). Dossiers' inline source labels (e.g. "GAO report, August 6, 2026") were plain, non-interactive text, contradicting that page's own banner claim that every number links to its source.
Corrected to
Indicators and Markets now use the same neutral rise/fall colors `VsPresidentsClient.tsx` already established for this exact situation, with a one-line legend added to both tables. Personnel's vote bars use two neutral, non-cost/benefit tones with updated explanatory copy. The onboarding banner's dismiss button is now absolutely positioned, immune to text-wrap. Every view's subtitle now renders on mobile at a smaller size instead of being hidden. Dossiers' beat-level source labels are now real links to the entry's actual sources, positioned next to the claim rather than requiring a scroll to a single button at the end of the section.
How the error happened
Found during a scheduled review of the live site before it was shared more widely; fixed and re-verified before publishing.
Full technical detail
Found in a 5-agent pre-publish review run against the live production site ahead of the archive being shared more widely, immediately before the readership was expected to grow. The color-token misuse is the same defect class already caught and fixed once in `presidentComparisons.ts`/`VsPresidentsClient.tsx` earlier this project's history. It had simply recurred in three more places that were never swept for the same pattern at the time. Verified end-to-end: typecheck, lint, 204/204 unit tests, clean build, 100/100 e2e, and a live check confirming each fix rendered correctly.
2026-08-15 · Promises view: three linked promises get a documented-tension note, plus a methodology note and a native/linked tagEditorial: no factual change to any entry; new context surfaced from existing sourced content
Published as
The `ice`, `edu`, and `s232` promise rows showed only the linked entry's short `status` field. Each entry's own effects data documents a fact that complicates or contradicts the promise's own wording: the majority of surged-area arrests being non-criminal-conviction (ice), halved staffing with documented civil-rights and aid-servicing backlogs (edu), and a net manufacturing-job loss from the tariffs meant to bring jobs back (s232). None of it reached the Promises page. The page also gave no account of why some promises read "Kept" and most read "In progress," and native vs. linked promises were distinguishable only by a subtle date-format difference.
Corrected to
Each of the three rows now carries a short, verbatim-quoted note pulled directly from that entry's own `effects[].estimates[].value`, sourced exactly as the entry already sources it, no new claim written for this page. A methodology paragraph explains the real rule (irreversible-by-ordinary-means is the bar for "Kept"; reversible-but-currently-in-force reads "In progress"). Every row now carries an explicit "own entry" / "linked verdict" tag.
How the error happened
Found in a fairness-panel review that ran against the two new views immediately after they shipped. Two of that panel's reviewers flagged the missing context on `ice`/`edu`/`s232` specifically; a third flagged the unexplained verdict mechanism; a fourth flagged the subtle native/linked distinction. All four were classified craft-fixable (presentation and completeness gaps, not a single fact in dispute) and fixed using only text already published elsewhere in the archive, per the same discipline as every other correction here.
2026-08-15 · Archive-wide: Milestones and Promises views added; one new entryMaterial: new entry and two new views added
Published as
The archive had no scale-ranked view of its own entries and tracked only 4 campaign promises (wall, aca, nowars, ukraine24), all sourced entirely from within their own entries. 96 entries total.
Corrected to
Two new views: Milestones (entries grouped by real, verbatim-sourced magnitude: money, people affected, jobs, institutional counts; never ranked across units and never labeled good or bad, per the archive's no-scores rule) and Promises (the 4 existing promise entries plus 12 promise-framed links into existing, already-sourced entries: tcja, judges, usmca, paris, vamission, daca, birthright, edu, s232, nato, ice, tiktok; each verdict read live from that entry's own standing, never a second copy of it). One new entry, `notaxtips` ("no tax on tips, overtime pay, and Social Security benefits"), researched and sourced from IRS.gov and the Joint Committee on Taxation's own JCX-35-25 revenue estimate plus PolitiFact and Kiplinger for the Social Security half, which was not actually enacted. 97 entries total.
How the error happened
Requested directly: a scale-based (not judgment-based) view of the record's biggest numbers, and a fuller campaign-promise tracker. Retyping existing policy entries (tcja, judges, etc.) to `type: "promise"` was considered and rejected. They are substantive standalone entries, not promise-tracking narratives, and retyping would have silently changed Ledger filter counts and Claims' delivery tally. A join table linking the promise's wording to the existing entry was used instead, so no entry's sourcing is duplicated or mutated.
2026-08-15 · Archive-wide: two contested-field wording edits, meaning unchangedEditorial: no factual change
Published as
The `futureact` entry's contested field joined two independent clauses with a semicolon into one long sentence. The `unemploy2019` entry's contested field referenced "the Tier 1/2 literature cited here", the archive's own internal source-tier shorthand, used inline in prose with no glossary link and no other instance of it anywhere in the 96 entries' free-text fields.
Corrected to
The `futureact` sentence is split into two at the semicolon (period, capitalized), same two clauses, same claim. The `unemploy2019` reference now reads "the primary-document and peer-reviewed literature cited here", substituting the glossary's own verbatim definitions of Tier 1 and Tier 2 (`src/lib/data/glossary.ts`: "Tier 1 is a primary document or federal statistics agency. Tier 2 is peer-reviewed research or a nonpartisan institution.") rather than inventing new phrasing.
How the error happened
Found in a readability pass that was checked carefully against the archive's own rules to confirm the meaning of each claim stayed exactly the same before and after. Only the wording changed.
Full technical detail
Found in a self-run readability pass scoped specifically to preserve claim, attribution, and hedging exactly, verified against `src/lib/invariants.test.ts` (21 tests, including the causal-language and attribution guards) before and after, both editorial, no factual change. Logged per the archive's own rule that changes are recorded whether or not they are substantive.
2026-08-14 · vs. Presidents: executive-orders comparison axis addedMaterial: new comparison axis added
Published as
The presidential comparison table covered debt added, debt per year, net jobs, and judges confirmed, four axes, none of them a measure of executive power itself.
Corrected to
A fifth row, "Executive orders issued," counted directly from the Federal Register's own publication dates within each term's window. Trump II's 276-so-far sits behind both Bush 43 (299) and Obama (295) at the same elapsed point, an inconvenient number for a "uniquely lawless" reading, published anyway.
How the error happened
Raised in a self-run fairness-panel pass: the one reader whose central concern is executive power regardless of party had no way to check whether the archive holds every administration to the same yardstick on the one thing they cared about most. Nothing existing on the page was wrong; a real gap in what could be checked is now closed.
2026-08-14 · Archive-wide: the caveat on every contested entry moved before its claimsEditorial: no factual change
Published as
Every entry's "contested ground" disclaimer (the field recording what's genuinely unresolved, including where the archive itself could be wrong) rendered after all of that entry's claims and estimates, for all 92 entries that carry one.
Corrected to
The disclaimer now renders immediately after Layer 2 (Status) and before Layer 3 (Measured effects), for every entry site-wide. A reader now sees the caveat before the specific claims it qualifies, not as a footnote after forming an impression from them. No disclaimer's text changed.
How the error happened
Raised in a self-run fairness-panel pass, using the January 6 entry as the concrete case: a reader hit five detailed, sourced claims (including the fake-elector scheme and the Pence pressure campaign) before ever reaching the line stating that Trump's own criminal culpability was never tested at trial. The fix is structural (one component, `EntryDrawer.tsx`), not a special case for one politically sensitive entry, because the same ordering problem existed for all 92.
2026-08-14 · Archive-wide: stat cards and tickers stopped coloring by political valenceEditorial: no factual change
Published as
Four separate stat displays (the new elapsed-term comparison (caught pre-publish), the "Trump II so far" cards on the vs.-Presidents page, the "Standing indicators" ticker at the top of the Overview view, and "Where the presidency stands right now" just beneath it) colored figures red or green by whether the number read as favorable or unfavorable to the administration. A drop in border apprehensions was colored green and captioned "the administration's central claimed achievement" in two of the four; debt, job losses, and a falling approval number were colored red in the rest. All of this sat on pages whose own banner states "no scores... color marks standing only, not good or bad."
Corrected to
All four now render a single neutral color. No number, label, or figure changed, only the color, which previously asserted a judgment none of these pages claim to make.
How the error happened
Noticed while reviewing a new feature that a figure which can only ever get worse (federal debt) was colored as if it were good news; checking the rest of the site for the same mistake turned up three more instances of it.
Full technical detail
Found first by rendering the new comparison feature and asking why federal debt (which only ever rises) was colored green; a subsequent grep for the same literal colors, then a targeted check of every semantic color token used near a stat card, found three more live instances of the identical pattern, one of them (Commonly Misread, logged separately) reached through a repurposed legal-standing token rather than a raw color. See docs/LESSONS.md for the full defect-class writeup.
2026-08-14 · Overview: headline figures reordered by date, not by accidentEditorial: no factual change
Published as
The Overview view's 23 headline tiles rendered in whichever order they had been appended to `headline.json` over time, which front-loaded costs (the first four tiles were cost, mixed, cost, cost) with both benefit-tagged tiles not appearing until well past the halfway point.
Corrected to
Tiles now sort newest-first by the date each figure is actually anchored to (the linked entry's date, or the term's own start date for a handful of running term-to-date tallies with no single entry). No tile's value, label, or `inc` classification changed.
How the error happened
Raised by two readers on opposite ends of the political spectrum in a self-run fairness panel, converging on the same complaint about what a visitor sees first on the site's own default landing page. Sorting by date rather than by valence was chosen deliberately: reordering to lead with favorable figures would not have removed the editorializing, only reversed its direction.
2026-08-14 · Commonly Misread: equal treatment across all three sectionsEditorial: no factual change
Published as
Of the page's three substantive sections ("favours him," "cuts against him," "nobody is right yet"), only "favours him" carried a colored border, a colored heading, and a working link to the sourced entries in the Ledger. The color used was STAND.ACTIVE (the "in force" legal-standing token) repurposed to mark this one section as the favorable one, with no equivalent path to verify the other two.
Corrected to
All three sections render identically: the same neutral border and heading color, and each with its own working link, "favours him" and "cuts against him" to their respective Ledger incidence filters, "nobody is right yet" to the contested-ground list further down the same page.
How the error happened
Found in a self-run fairness-panel pass: only one of the page's three sections had a highlighted color and a working link, making it look more credible than the other two even though none of the underlying facts or sources had changed.
Full technical detail
Found in a self-run fairness-panel pass. Not one word of the page's content changed (every claim and every source is exactly as it was) but a legal-standing color repurposed as a happiness signal, applied to only one of three sibling sections, is the same defect already found and fixed four times elsewhere this session in a different shape (see docs/LESSONS.md). Logged per the archive's rule that changes are recorded whether or not they are substantive.
Published as
Two claim headings used narrative framing not matched elsewhere in the entry: "An organized effort submitted certificates from fake electors in seven contested states," and "The campaign pressured Vice President Pence to reject or delay certification of the electoral count." A third heading, "Legal consequences for the events themselves," was vague relative to its own sourced content (the Senate acquittal and Trump v. Anderson).
Corrected to
The two claim headings are now passive and procedural, matching the register of the entry's other headings, no source, estimate, or fact changed, only the framing verb and voice. The third now reads "The House impeached and the Senate acquitted; courts later barred Section 3 disqualification," naming what it actually documents instead of a placeholder phrase.
How the error happened
Found in a self-run fairness-panel pass, not by a reader. The entry's facts were never in dispute (every claim already carried its full, sourced detail in the estimates below the heading) but a heading's own word choice is itself an editorial act, and this archive's rule is that changes are logged whether or not they are substantive.
2026-08-10 · Roadmap: accessibility claimMaterial: published claim overstated
Published as
A completed roadmap item read "Accessibility: WCAG AA contrast, 44px targets, skip link, main landmark, drawer focus management."
Corrected to
The item reads "WCAG AA contrast (4.5:1) and AA target size (24px)," and AAA target size (44px) is listed separately as open. A new audit row measures control sizes live from the rendered page on every load.
How the error happened
The claim was produced by a static scan that only saw controls with declared pixel dimensions; every control sized by padding was invisible to it, and roughly 27 sit between 24px and 44px. The interface does meet the AA bar the sentence invoked, so the interface was never the defect. The claim was. This is the same failure class as the label-count correction logged the same day: a figure asserted in prose rather than measured, and it is logged rather than quietly reworded.
Published as
Status read that tariffs "terminated February 24, 2026," and refund exposure was given as a single figure, "near $166 billion," sourced to "trade-law practitioner analyses."
Corrected to
CBP announced it would stop assessing IEEPA duties on February 22, 2026 (CSMS #67834313). Refund exposure is now shown as a spread: up to $175 billion (Penn Wharton Budget Model) and more than $170 billion collected through the ruling date (PwC analysis of CBP and Treasury data), with Justice Kavanaugh’s dissent noting refunds may be owed even where importers passed costs on.
How the error happened
Found in an internal fact-check pass, not reported by a reader. Two defects: the date was wrong, and a single practitioner figure was standing where the archive’s own rules require a sourced spread. The stale number had propagated to the overview tiles, the vitals strip and the dossier, all of which were corrected together.
2026-08-10 · Archive-wide: source labelling and spellingEditorial: no factual change
Published as
151 distinct source-lean labels, including pure synonyms ("Academic" / "Peer-reviewed academic" / "Academic / peer-reviewed"), and British and American spellings mixed roughly evenly across 36 instances.
Corrected to
Synonym clusters collapsed to a controlled vocabulary; compound labels carrying real information were kept verbatim. The live count is published in the integrity audit on the Masthead rather than restated here, so the two can never drift apart. Spelling unified to American, preserving official titles that are British by name (WHO Programme Budget, NATO Defence Expenditure).
How the error happened
Taxonomy drift and inconsistent spelling do not change a single fact, but they are exactly what a hostile reader cites as evidence of carelessness. Recorded here because the archive’s rule is that changes are logged whether or not they are substantive.
Published as
Status read "Partially implemented; multiple actions litigated," and the savings-claim effect cited press verification of documentation errors.
Corrected to
Status reads "Concluded July 4, 2026; savings claims found substantially unverifiable." Three GAO findings from the August 6, 2026 audit replace the press-sourced characterization, and the entry now records that the audit was requested by two Democratic senators.
How the error happened
GAO published its audit two days ago. The prior entry was accurate when written and stale afterwards, which is the failure mode this archive is most exposed to, and the reason every status carries a verification date.
Published as
Stated that Section 232 tariffs "were struck down alongside the IEEPA tariffs in February 2026."
Corrected to
Section 232 tariffs remain in force. The February 2026 ruling addressed IEEPA only; Section 232 rests on a separate statute with its own investigation requirement.
How the error happened
Editor conflated two tariff authorities while summarizing the ruling. Caught by a reader who cited the executive order text, which explicitly preserved Section 232 and Section 301 actions.
Published as
Effect claim "Federal deficits increase relative to prior law" was labeled Contributory.
Corrected to
Relabeled Direct. A CBO score of an enacted statute is a direct budgetary consequence of that statute, not one input among several.
How the error happened
Internal audit of attribution consistency across all Taxes & budget entries. Three entries were relabeled in the same pass.
Published as
Status detail said "roughly 450 miles were built."
Corrected to
Added that approximately 80% of that mileage replaced pre-existing barrier rather than adding new mileage, per CBP’s own reporting.
How the error happened
The original phrasing was accurate but incomplete in a way that invited misreading. Reader-submitted.
Published as
Status read "In effect; under Supreme Court review."
Corrected to
Status read "Invalidated, collection ceased February 22, 2026; replaced under Section 122." Verification date advanced.
How the error happened
Scheduled status review triggered by the docketed decision date. Logged because status changes are substantive, not cosmetic.
Published as
Cited CBO’s 13-million projection without noting CBO’s later revision.
Corrected to
Both the original projection and CBO’s published methodological correction are shown together.
How the error happened
Citing a projection that its own author has since corrected, without saying so, is the exact failure this archive exists to avoid.
2026-08-13 · Archive-wide: source citation targetsEditorial: no factual change
Published as
40 of 215 source URLs pointed at a publisher's homepage rather than the document the source's own label named. "Trump v. CASA, Inc. (2025)" resolved to supremecourt.gov; "Navigable Waters Protection Rule, Federal Register" resolved to federalregister.gov.
Corrected to
33 of the 40 now resolve to the specific document. Each was confirmed by fetching the candidate and matching its content against the label before the link was changed: the CASA link resolves to the slip opinion captioned TRUMP v. CASA, INC., No. 24A884; the emoluments link to the docket reading "Judgment VACATED and case REMANDED with instructions to dismiss the case as moot". Seven still point at a homepage, and a test holds that number so it can only fall: both sources on the Gaza ceasefire entry, both on the Soleimani entry, and one each on Space Force, Syria, and hospital price transparency. Six of those name a plural or open-ended body of material ("reporting and analysis", "statements", "documents", "reports") with no single document behind them, so any one link would misstate what is being cited. The seventh cannot be fixed at all: the January 2020 War Powers notification to Congress was classified in its entirety and has never been published, so no public URL for it exists.
How the error happened
No claim, figure, attribution level or standing changed, only which page a citation opens. It is logged anyway, for the same reason the source-labelling pass on 2026-08-10 was: the archive's rule is that changes are logged whether or not they are substantive, and a citation that silently starts pointing somewhere new is precisely the kind of change a reader is entitled to see. One error was caught this way and is corrected separately below.
Published as
The entry's executive-order source was deep-linked to Executive Order 14151 (Ending Radical and Wasteful Government DEI Programs and Preferencing). The entry states four times (in its summary, its action, its status detail, and a Direct-attribution effect claim sourced to "Executive order text") that Executive Order 11246 was revoked. EO 14151 does not mention EO 11246, revocation, or affirmative action anywhere in its text.
Corrected to
Executive Order 14173 (Ending Illegal Discrimination and Restoring Merit-Based Opportunity), signed 21 January 2025, is cited alongside it. That is the order that actually revokes EO 11246. Both are kept, because the entry's action text describes the executive orders of 20–21 January 2025 as a set.
How the error happened
The homepage link this replaced asserted nothing; a deep link asserts that a specific document supports the claim beside it. Checking the new URL against the source's label was not sufficient. The label read "Executive orders on federal DEI programs", which EO 14151 satisfies, while the entry's central factual claim rests on a different order. A citation has to support the claim, not merely the label. Found in a self-run review pass, not by a reader.
Published as
The source labelled "American Hospital Association v. Azar, D.C. Circuit (2020)" linked to https://www.cadc.uscourts.gov/, the court's homepage. A reader clicking to verify that the rule survived challenge landed on a front page. It was left that way on the recorded finding that the D.C. Circuit publishes opinions under unguessable GUID paths and that the govinfo USCOURTS package IDs do not resolve.
Corrected to
The source is relabelled "American Hospital Association v. Azar, No. 20-5193 (D.C. Cir. 29 December 2020), slip opinion" and links to the full opinion text. Both halves of the earlier finding were re-checked and both still hold: the cadc.uscourts.gov path CourtListener recorded for this opinion now returns 404, and all four candidate govinfo package paths return a not-found page. The opinion was located through CourtListener's search API and read in a real browser to confirm the docket number, the 29 December 2020 filing date, the price-transparency subject matter, and the disposition affirming summary judgment for the Secretary before the url was written.
How the error happened
The document was reachable; the earlier conclusion was that the court's own copy was unreachable, which is a different statement and stayed true. Linking a stable repository copy of the slip opinion beats linking a homepage that asserts nothing. Logged because changing which document a published citation resolves to is a change to the citation, and the archive logs changes whether or not they are substantive.
2026-08-13 · Archive-wideEditorial: no factual change
Published as
Six source urls point at a publisher's site rather than at the document their label names, because each label names a plural or open-ended body of material, or in one case a document that is not public. The reasons were recorded in an internal document. On the site itself the links were indistinguishable from a citation that had simply gone stale.
Corrected to
Each of the six carries a structured provenance note, shown to the reader beside the link, saying why it resolves to a publisher rather than a document. The War Powers notification is marked as unreleased and carries CRS report R46148 as a companion that describes it. No claim, figure, or attribution changed.
How the error happened
An unexplained homepage link reads as a broken citation, and the archive's traceability promise is the whole basis for trusting it. The explanation belongs where the reader is, not in a repository file. The count of such links is separately capped by a test that only moves down, so this disclosure cannot become a way to add more of them.
Published as
The Flaaen & Pierce Federal Reserve source pointed at a URL ending "…2018-2019-tariffs.htm", which returns a Federal Reserve "Page not Found". The stored address was a truncation of the real one, the paper's slug continues "…-on-a-globally-connected-us-manufacturing-sector".
Corrected to
The full URL, confirmed to load in a real browser with the paper's own title. The citation is unchanged; only the address it resolved to was wrong.
How the error happened
A citation that 404s is worse than no citation: it looks checkable and is not. Found by a link check over all 579 distinct source URLs in the archive rather than by a reader hitting it. The same sweep is now a script, so the next dead link surfaces without anyone thinking to look.
Published as
The PIIE Phase One tracker source pointed at /research/piie-charts/chinas-purchases-us-goods-under-phase-one-trade-agreement, which returns PIIE's "Page Not Found". PIIE reorganised its chart URLs under a year segment at some point after the citation was written.
Corrected to
The tracker's current address, confirmed to load with the title "US-China phase one tracker: China's purchases of US goods". Recorded as the URL the site settles on after its redirect, so the citation does not depend on that redirect surviving.
How the error happened
Same sweep as the entry above. Link rot is not a hypothetical for an archive whose whole claim is that every figure is traceable. It is the failure mode that arrives on its own, without anybody editing anything.
Published as
The source labelled "FDA COVID-19 vaccine authorization record" pointed at an fda.gov page that returns "Page Not Found". FDA reorganised the section and did not redirect: their own current COVID-19 landing page still links to a "COVID-19 Vaccines" node that 404s as well, so there is no live successor to follow.
Corrected to
An Internet Archive snapshot of the same FDA page taken 22 January 2025, confirmed to load and to contain the section "COVID-19 Vaccines Approved or Authorized for Emergency Use" along with the individual authorisations. The label says plainly that it is an archived snapshot and that FDA removed the live page, so nobody mistakes it for a current agency URL.
How the error happened
Several plausible replacement paths on fda.gov were tried and every one 404d. Substituting a guessed URL that happens to return 200 would be worse than the dead link, because it would look verified while pointing at a document nobody checked against the claim. An archived copy of the document actually cited is the honest repair, and it does not rot again.
Published as
The entry stated that presidential-family crypto ventures had drawn ethics scrutiny, sourced to a single estimate whose source field read only "Government ethics organizations". No group named, no dollar figure anywhere in the entry despite one being disclosed and publicly reported.
Corrected to
Trump's own 2025 annual financial disclosure (OGE Form 278e, filed July 1, 2026) reports roughly $1.4B in cryptocurrency income for the year, added as its own Direct-attribution effect with the primary filing plus two independent outlets corroborating the same breakdown. The characterization claim is now attributed by name to CREW and Public Citizen, each with a dated report and, for Public Citizen, a named research director's quote, and is paired with an on-the-record White House denial so the claim does not rest on advocacy sources alone.
How the error happened
An anonymous "government ethics organizations" citation reads as unaccountable no matter which direction it leans, and it was flagged by personas across the political spectrum in a self-run fairness panel. Named sources and a real figure are checkable; a generic one is not.
Published as
The entry covered the certification delay, the impeachment and acquittal, and the dismissed federal case, but its effects never mentioned the fake-elector scheme or the pressure campaign on Vice President Pence, the documented conduct at the center of the House Select Committee's findings and the DOJ indictment.
Corrected to
Two new effect claims document the submitted fake-elector certificates in seven states and the January 4, 2021 Oval Office meeting pressuring Pence, each sourced to the House Select Committee's final report plus John Eastman's disbarment, a genuinely adjudicated finding, unlike Trump's own dismissed case, since the California State Bar Court found him culpable on 10 of 11 counts specifically for this conduct, upheld by the California Supreme Court in April 2026. The contested field is extended to keep the same distinction the entry already drew: the underlying events are documented and, in Eastman's case, adjudicated; whether Trump personally bears criminal responsibility was never tested at trial.
How the error happened
A fairness review built to catch soft-pedaled language flagged that this entry was missing conduct that is genuinely part of the documented record. The gap held up on review and the entry was filled in.
Full technical detail
The omission was flagged during a self-run fairness-panel pass, by one persona in that panel built specifically to distrust euphemism and false balance. And it held up: the conduct is core to the documented record regardless of how the unresolved legal question about Trump himself is framed, and its absence was a real completeness gap, not a framing choice.
Published as
The Disputed "Legality under domestic and international law" claim paired the administration's own position (a DOJ opinion it has declined to release, which does not itself assert legality) against a named Democratic legislator, Rep. Jim Himes, calling the operation "clearly illegal." No independent or right-leaning legal-scholar defense of the Article II / 2002 Iraq AUMF theory was cited, even though this archive cites exactly that kind of counterweight elsewhere on comparable questions, Justice Alito's dissent on the National Guard entry, and "minority scholarship... cited by the administration" on the birthright-citizenship entry.
Corrected to
Added a fourth estimate: law professor Jonathan Turley's published legal argument (Fox News opinion, January 3, 2026) that the capture required no congressional approval, citing the 1989 capture of Manuel Noriega and the pattern of unilateral presidential use of lethal force by both parties as controlling precedent. Labeled with a lean distinct from both the administration's own statement and the named legislators on either side, matching the classifier already used for the soleimani and birthright entries' academic estimates.
How the error happened
Flagged by a fairness review as an asymmetry in how rigorously this entry sourced the administration's strongest legal defense, compared to sibling war-powers entries. The administration's own estimate, Himes' quote, and the roll-call result are untouched, and no claim about the operation's actual legality was added or changed, the entry still declines to characterize an opinion it cannot read. This only adds a real, named academic source making the case the administration's own (undisclosed) opinion does not make in the record.
2026-08-16 · Site-wide: 'Cite this entry' permalink pointed at the abandoned Vercel domain, not the live oneMaterial: citation-facing bug, no documented fact changed
Published as
Every entry drawer's "Cite this entry" block built its permalink from `SITE_ORIGIN` in `src/lib/citation.ts`, which still read `https://the-record-taupe.vercel.app` after `thetrackrecord.org` became the live, canonical domain. A reader citing any entry got a URL on an abandoned Vercel subdomain instead of the real address, directly beside the drawer's own sentence promising "this entry has a stable address and will not be silently rewritten," the one claim on the page specifically about citation durability.
Corrected to
`SITE_ORIGIN` now reads `https://thetrackrecord.org`. Every consumer derives from that one constant (the drawer's citation text and permalink, `layout.tsx`'s canonical/OpenGraph/JSON-LD urls, `sitemap.xml`, `robots.txt`, `feed.xml`, and the admin archive-snapshot triggers) so nothing else needed a separate edit. `parseEntryId.test.ts` now imports `SITE_ORIGIN` instead of hardcoding the old domain string, so this can't drift out of sync again. Also added a permanent (308) redirect in `middleware.ts` from the old `the-record-taupe.vercel.app` host to the matching path and query on `thetrackrecord.org`, so a citation already made against the old domain before this fix shipped still resolves to the real page instead of a second, uncanonical copy of it.
How the error happened
A wrong domain in a citation permalink is exactly the citation-facing fact invariant 8 exists to cover, even though no entry's documented content changed. Logged per invariant 8: changes are recorded whether or not they are substantive.
Open questions register
Questions this archive cannot currently answer, recorded so that silence is never mistaken for absence of evidence, or for a hidden conclusion. Each carries the reason it is open and the data that would close it.
Did tariff policy produce durable reshoring?
Manufacturing construction spending rose sharply, but employment and output effects lag construction by years, and the legal basis for the tariffs changed twice. No credible estimate can separate the policy effect from the CHIPS and IRA capital cycle yet.
Revisit when 2027-28 census manufacturing data lands.
Net fiscal effect of the 2025 workforce reductions.
Requires severance outlays, rehiring costs, lost IRS enforcement revenue, contractor substitution, and litigation costs, none of which are published in a single reconciled series. Every currently circulating number omits at least two of these.
Revisit after GAO and agency IG reviews report.
Coverage effects of OBBBA’s Medicaid provisions.
The provisions phase in after 2026. Current figures are projections, not measurements, and this archive distinguishes the two.
Revisit against CPS and NHIS coverage data from 2028 forward.
Whether the 2024 New York prosecution was legally sound.
Genuinely disputed among credentialed practitioners, and the appeal is pending. The archive records the conviction as fact and the legal dispute as unresolved.
Revisit on appellate decision.
Submitting a correction
A correction is accepted when it identifies the specific claim, cites a document a reader can open, and states what the claim should say instead. Disagreement with an entry’s framing is not a correction. But if a framing implies a judgment the evidence does not support, that is a correction, and one worth making.
Every submission is answered, including the ones that are declined, with the reason on the record.