Skip to content
The Record

Corrections

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 · 100 entries · last change August 18, 2026
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.
  • Click a figure that has an entry to see the documents and how strongly the number can be tied to the action (). A few macro counts (gross debt, this-term jobs, this-term judges) have no matching entry, so they stay unlinked rather than pointed at the wrong document.
  • 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
158
Material: changed a claim
57
Reader-submitted
50
Self-found: not reader-submitted
108

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
The source labeled New York State Unified Court System case record linked to the civil eCourts homepage, a portal for civil cases, not the criminal indictment.
Corrected to
The source is Justice Merchan's January 3, 2025 Decision and Order in People v. Trump, Ind. 71543-23, denying the Clayton motion, upholding the 34-count verdict, and setting sentencing for January 10, 2025. The CBS sentencing story and Penal Law § 175.10 remain.
How the error happened
The conviction is a criminal case. Clicking that source used to open New York's civil eCourts portal. It now opens the January 2025 court order that kept the verdict in place and set the sentencing date.
Full technical detail
Invariant 9 Bin A: a civil-court homepage standing in for a named criminal decision. Logged per invariant 8.
Published as
A source labeled CDC ACIP charter and membership record linked to cdc.gov/vaccines/acip/. The AAP v. Kennedy source linked to the CourtListener docket index rather than the stay order.
Corrected to
The reconstitution source is HHS's June 9, 2025 announcement removing all 17 sitting ACIP members. The litigation source is the March 16, 2026 memorandum and order (D. Mass. 1:25-cv-11916, Doc. 291) staying the new appointments and the reconstituted committee's votes. The 2009 HHS OIG ethics review is unchanged.
How the error happened
The entry already named the June 2025 reconstitution and the March 2026 court stay. Those sentences now open the HHS announcement and the stay order, not a CDC landing page and a case index.
Full technical detail
Invariant 9 Bin A: a committee homepage and a docket index standing in for named documents. Logged per invariant 8.
Published as
A source labeled National Taxpayer Advocate annual reports linked to taxpayeradvocate.irs.gov/reports/, an index of every year's report.
Corrected to
The source is the 2025 Annual Report to Congress Executive Summary, which records FY2025 identity-theft case inventory of about 316,000 and an average 21-month resolution time, and criticizes the IRS telephone-service measure.
How the error happened
The IRS entry already cited the Taxpayer Advocate on phone service and identity-theft backlogs. That source now opens the 2025 report instead of a list of every year's reports.
Full technical detail
Invariant 9 Bin A: a reports index standing in for a named annual report. Logged per invariant 8.
Published as
VA announcements linked to va.gov/opa/pressrel/. Congressional hearing records linked to congress.gov/committees, a list of every committee.
Corrected to
The VA source is the department's July 7, 2025 announcement that staff would fall by nearly 30,000 by the end of FY2025 through attrition rather than a large RIF. The congressional source is Rep. Timothy Kennedy's August 5, 2025 letter in the House Veterans' Affairs Committee record, which states the leaked March target exceeded 80,000 positions and was later revised to 30,000.
How the error happened
The entry already said the plan started near 80,000 and was scaled back to about 30,000. Those sentences now open the VA's own 30,000 announcement and the House letter that records both figures, not a press-release dump and a list of every congressional committee.
Full technical detail
Invariant 9 Bin A: an announcements index and a committees hub standing in for named documents. Logged per invariant 8.
Published as
A source labeled FCC docket records linked to fcc.gov/ecfs/, the search page for every FCC filing.
Corrected to
The source is FCC 25-43 (July 24, 2025), the Commission's memorandum opinion and order on the Paramount Global transfer of control, MB Docket 24-275. The AP v. Budowich injunction PDF is unchanged.
How the error happened
The press entry already described regulatory pressure on broadcasters with transactions pending. That source now opens the Paramount transfer order instead of the FCC's whole-docket search page.
Full technical detail
Invariant 9 Bin A: a docket search hub standing in for a named Commission order. Logged per invariant 8.
Published as
A source labeled OECD comparative excess mortality linked to oecd.org/health/.
Corrected to
The source is OECD Health at a Glance 2021, which reports excess deaths across OECD countries in 2020 and the first half of 2021 and a 1.6-year drop in US life expectancy, among the largest in the comparison set.
How the error happened
The COVID entry already compared US excess mortality with peer countries. That source now opens the OECD 2021 Health at a Glance report instead of OECD's health homepage.
Full technical detail
Invariant 9 Bin A: an organization topic homepage standing in for a named comparative report. Logged per invariant 8.
Published as
A source labeled FEMA budget and staffing documents linked to fema.gov/about/reports-and-data.
Corrected to
The source is the DHS Fiscal Year 2026 Budget in Brief, FEMA chapter, which states FEMA's FY2026 request and FTE levels. GAO-26-108427 remains the staffing-readiness citation.
How the error happened
The FEMA entry already pointed at budget and staffing documents. That click now opens the FY2026 Budget in Brief instead of FEMA's reports landing page.
Full technical detail
Invariant 9 Bin A: a reports index standing in for a named budget document. Logged per invariant 8.
Published as
The source labeled Congressional Record, joint session January 6-7, 2021 linked to congress.gov's Congressional Record browse hub, with a note that no single URL identified the sitting.
Corrected to
The source is the House Congressional Record PDF for January 6, 2021, which contains the joint session counting electoral votes.
How the error happened
The entry already named the January 6 joint session. Clicking that source used to open a search page for every day's Congressional Record. It now opens the January 6, 2021 House Record that contains the sitting.
Full technical detail
Invariant 9 Bin A: a browse hub standing in for a named sitting of Congress. Logged per invariant 8.
Published as
Two sources labeled as mediation reporting and State Department statements linked to cfr.org and state.gov homepages.
Corrected to
The clickable sources are the White House Comprehensive Plan to End the Gaza Conflict (Sept. 29, 2025), UN Security Council Resolution 2803 (2025), and CFR's guide to the twenty-point deal.
How the error happened
The Gaza entry already described a 20-point US-brokered framework. Its sources used to open CFR's and the State Department's front pages. They now open the plan text, the UN resolution that endorsed it, and a CFR explainer of that plan.
Full technical detail
Invariant 9 Bin A: publisher homepages standing in for named documents. Logged per invariant 8.
Published as
A source labeled as Space Force organization and budget documents linked to spaceforce.mil's homepage.
Corrected to
The source is the DoD Comptroller's FY2026 Operation and Maintenance Overview, which includes the Space Force's own budget line. The FY2020 NDAA remains the establishment citation.
How the error happened
The entry already said the Space Force has its own budget line. That sentence now opens the FY2026 O&M overview instead of the service's front page.
Full technical detail
Invariant 9 Bin A: a service homepage standing in for a named budget document. Logged per invariant 8.
Published as
The War Powers report linked to congress.gov's homepage, with a note that the document is classified. DoD casualty reporting linked to defense.gov's homepage.
Corrected to
The War Powers source opens CRS R46148, the public record that the January 2020 notification was submitted and classified in full. The casualty source is the Associated Press report of the Pentagon's February 10, 2020 statement that 109 service members had been diagnosed with mild TBI after the Al Asad strike. The Pentagon's own release page no longer resolves.
How the error happened
Clicking the War Powers source used to open congress.gov's front page, even though the report itself is classified. It now opens the CRS paper that records that fact. The casualty source now opens the AP report of the Pentagon's February 2020 TBI count instead of the Defense Department homepage.
Full technical detail
Invariant 9 Bin A: homepages standing in for a named CRS report and a named Pentagon casualty update. Logged per invariant 8.
Published as
The 354-60 House disapproval linked to clerk.house.gov/Votes, a list of every House vote. OCHA situation reports linked to unocha.org's homepage.
Corrected to
The House source is roll call 560 (Oct. 16, 2019), H.J. Res. 77, 354-60. The OCHA source is Flash Update 7 (16-18 October 2019), which states that at least 165,000 people had been displaced in just over a week. Live ReliefWeb returns an empty challenge page to ordinary fetchers, so the citation is the Internet Archive copy of that same PDF.
How the error happened
The entry already said the House voted 354-60 and that OCHA reported mass displacement. Those sentences now open that roll call and that October 2019 flash update, not a list of every House vote and OCHA's front page.
Full technical detail
Invariant 9 Bin A: collection hubs standing in for a named roll call and a named situation report. Logged per invariant 8.
Published as
The source labeled Phang v. Blanche, No. 1:26-cv-01417 linked to govinfo.gov's entire U.S. Courts collection, with a note that no single URL on that system identified the case.
Corrected to
The June 25, 2026 preliminary-injunction order (D.D.C. 1:26-cv-01417, Judge Sullivan) is linked as a PDF.
How the error happened
The entry already named the Phang v. Blanche case. Clicking Sources used to open a government search page covering every federal court. It now opens the June 2026 injunction order.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named order. Logged per invariant 8.
Published as
The source labeled as the Supreme Court opinion linked to Lisa Cook's Wikipedia page. The contested field still said this was a live case, even though status already recorded the June 29, 2026 holding that the removal was unconstitutional.
Corrected to
The source is the Court's PDF in Trump v. Cook, No. 25A312 (June 29, 2026). Contested text now states that the attempted removal was resolved and Cook remains in office.
How the error happened
Clicking the Supreme Court source used to open Wikipedia. It now opens the Court's own opinion. The entry also no longer describes a decided case as still live.
Full technical detail
Invariant 9 Bin A: a Wikipedia page standing in for a named opinion, and a status field that contradicted contested. Logged per invariant 8.
Published as
A source labeled "District court orders on Guard deployments" linked to govinfo.gov's entire U.S. Courts collection.
Corrected to
Oregon v. Trump, D. Or. TRO (Oct. 4, 2025) and Illinois v. Trump, N.D. Ill. TRO (Oct. 9, 2025) are linked as PDFs.
How the error happened
The Guard-deployment court fights were already in the text. The source list now opens the Oregon and Illinois temporary restraining orders instead of a search page of every federal court.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for named orders. Logged per invariant 8.
Published as
Harvard College v. HHS linked to govinfo.gov's entire U.S. Courts collection.
Corrected to
The September 3, 2025 D. Mass. memorandum and order (No. 1:25-cv-11048) is linked as a PDF.
How the error happened
The Harvard case was already named. The source now opens the September 2025 court memorandum instead of a government search page.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named opinion. Logged per invariant 8.
Published as
Perkins Coie LLP v. DOJ linked to govinfo.gov's entire U.S. Courts collection.
Corrected to
The May 2, 2025 D.D.C. order granting summary judgment (No. 1:25-cv-00716) is linked as a PDF.
How the error happened
The Perkins Coie case was already named. The source now opens the May 2025 order instead of a government search page.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named order. Logged per invariant 8.
Published as
A source labeled "Court order vacating the 2024 rule" linked to govinfo.gov's entire U.S. Courts collection.
Corrected to
Tennessee v. Cardona, E.D. Ky., January 9, 2025 summary-judgment order is linked as a PDF. That order vacates the 2024 rule itself (APA vacatur), which is the nationwide restoration of the 2020 rule already stated in statusDetail.
How the error happened
The entry already said a January 2025 court order vacated the 2024 Title IX rule nationwide. That sentence now opens the Kentucky court's January 9 order instead of a search page of every federal court.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named order. Logged per invariant 8.
Published as
A source labeled "Docket and subsequent dismissal record" linked to govinfo.gov's entire U.S. Courts collection.
Corrected to
The November 25, 2024 D.D.C. opinion dismissing the superseding indictment in United States v. Trump, No. 23-cr-257, is linked as a PDF.
How the error happened
The dismissal of the D.C. criminal case was already in the text. The source now opens that November 2024 opinion.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named opinion. Logged per invariant 8.
Published as
A source labeled "Post-ruling class certification dockets" linked to govinfo.gov's entire U.S. Courts collection. No single docket was named.
Corrected to
That hub is gone. The clickable sources are the Trump v. CASA opinion and Trump v. Barbara, which is the class-action follow-on the entry already uses to show that broad relief continued after universal injunctions ended.
How the error happened
One source used to dump you on a government search page labeled as later class-action dockets, without naming any. That link is gone. The two Supreme Court opinions the entry actually relies on remain.
Full technical detail
Invariant 9 Bin A: a collection hub that did not identify a document. Logged per invariant 8.
Published as
Storch v. Hegseth linked to govinfo.gov's entire U.S. Courts collection.
Corrected to
The September 24, 2025 D.D.C. memorandum opinion (No. 1:25-cv-00415) is linked as a PDF. That opinion finds the notice statute was not followed and declines reinstatement.
How the error happened
The inspector-general lawsuit was already named. The source now opens the September 2025 opinion instead of a government search page.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named opinion. Logged per invariant 8.
Published as
Associated Press v. Budowich linked to govinfo.gov's entire U.S. Courts collection.
Corrected to
The April 8, 2025 D.D.C. memorandum opinion granting a preliminary injunction (No. 1:25-cv-00532) is linked as a PDF.
How the error happened
The AP case was already named. The source now opens the April 2025 injunction opinion instead of a government search page.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named opinion. Logged per invariant 8.
Published as
A source labeled as Revolution Wind v. Burgum linked to BOEM's project page, with a note that the court rulings lived elsewhere.
Corrected to
The September 22, 2025 D.D.C. hearing transcript of Judge Lamberth's preliminary-injunction ruling (No. 1:25-cv-02364) is linked as a PDF. BOEM's leasing records remain as a separate source.
How the error happened
The entry already said a federal judge ordered Revolution Wind work resumed. That sentence now opens the court transcript of that ruling, not the project's permitting page.
Full technical detail
Invariant 9 Bin A: a project page standing in for a named court ruling. Logged per invariant 8.
Published as
A source labeled as the SDNY indictment in United States v. Maduro Moros linked to the U.S. Attorney's Office homepage.
Corrected to
The superseding indictment (S2 11 Cr. 205) is linked as a Justice Department PDF.
How the error happened
The Maduro indictment was already named. The source now opens that indictment instead of the prosecutor's front page.
Full technical detail
Invariant 9 Bin A: a homepage standing in for a named charging document. Logged per invariant 8.
Published as
A source labeled as GAO's Market Facilitation Program review linked to GAO's reports-and-testimonies collection, after an earlier report ID 404'd.
Corrected to
The source is GAO-22-468 (December 2021), the report that found 2019 MFP payments for some commodities exceeded USDA's own trade-damage estimates.
How the error happened
The farm-aid entry already cited GAO's finding that some Market Facilitation Program payments exceeded measured trade damage. That sentence now opens the specific 2021 report instead of GAO's whole reports list.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for a named GAO report. Logged per invariant 8.
Published as
A source labeled as the June 1, 2026 D.C. Circuit ruling in Talbott linked to the Wikipedia page for Executive Order 14183.
Corrected to
The source is the D.C. Circuit opinion in Talbott v. United States, No. 25-5087 (June 1, 2026). The Federal Register text of the order was already a separate source.
How the error happened
The entry already named the June 2026 D.C. Circuit ruling. Clicking that source used to open Wikipedia. It now opens the court's opinion.
Full technical detail
Invariant 9 Bin A: a Wikipedia page standing in for a named appellate opinion. Logged per invariant 8.
Published as
A source labeled as Kevin Warsh's confirmation timeline linked to his Wikipedia page.
Corrected to
The source is Senate roll call 120, 119th Congress (May 13, 2026), the 54-45 confirmation of Warsh as Fed chair. The Board roster remains.
How the error happened
The entry already said the Senate confirmed Warsh 54-45. That sentence now opens the roll-call page instead of Wikipedia.
Full technical detail
Invariant 9 Bin A: a Wikipedia page standing in for a named Senate vote. Logged per invariant 8.
Published as
The first two clickable sources were NPR's National Guard deployments series and Capital B's Guard city tracker. The entry is about interior ICE enforcement, custody deaths, and named shootings. Neither URL supported those claims. The 91% border-apprehension figure named CBP but linked only FactCheck. The 33 custody deaths named ICE but linked a detention-management page, not death reporting. The El Paso homicide ruling named the medical examiner with no URL.
Corrected to
Sources are NPR's report on the DOJ Chicago filing (598 of 614 arrested, 97%, had no criminal record), NPR's April 10, 2026 report on the Minneapolis shootings of Renee Macklin Good and Alex Pretti, CBP's Southwest Land Border Encounters table, ICE Detainee Death Reporting, the Associated Press account of the El Paso County Medical Examiner homicide ruling, plus the existing KFF, FactCheck, Pew, and ICE detention-management pages. The Chicago 97% figure is now in the estimate next to the majority-non-criminal claim.
How the error happened
Clicking the ICE entry's first two sources used to open pages about National Guard deployments, which is a different subject. They now open the Chicago arrest filing and the Minneapolis shooting reporting the text was already using. The border number now also links CBP's own table, and the custody-death count links ICE's death-reporting page.
Full technical detail
Invariant 9 Bin A: a citation that resolved to the wrong document. Logged per invariant 8.
Published as
The Eastman disbarment cited UPI and CNN. Barr's December 2020 no-outcome-determinative-fraud statement and Georgia's risk-limiting audit were named in estimates with no URL.
Corrected to
Clickable sources are the California Supreme Court's April 15, 2026 conference order in Eastman on Discipline (S292011), the State Bar of California's announcement of that order, Barr's December 1, 2020 Associated Press interview, and the Georgia Secretary of State's 2020 risk-limiting audit page. UPI and CNN are no longer the Eastman citations.
How the error happened
The entry already said California's high court disbarred John Eastman, that Barr told the AP there was no fraud on a scale that would change the 2020 outcome, and that Georgia's audit confirmed the result. Those sentences now open the court order, the AP interview, and the Secretary of State's audit page instead of news rewrites.
Full technical detail
Invariant 9 Bin A: the court order and the named official records were not clickable. Logged per invariant 8.
Published as
The source labeled "EDVA docket and dismissal opinion" linked to govinfo.gov's entire U.S. Courts collection, with a provenance note admitting no single URL on that system identified the cases.
Corrected to
The November 24, 2025 opinions dismissing United States v. Comey (1:25-cr-00272) and United States v. James (2:25-cr-00122) are linked as PDFs. Both held the interim U.S. Attorney's appointment invalid and dismissed without prejudice. The Appointments Clause / 28 U.S.C. § 546 citation is unchanged.
How the error happened
The entry said a federal judge dismissed both cases because the prosecutor who brought them was not lawfully appointed. Clicking Sources used to dump you on a government search page covering every federal court. It now opens the two dismissal opinions.
Full technical detail
Invariant 9 Bin A: a collection hub standing in for named opinions. Logged per invariant 8.
Published as
One estimate slot held both "$4.1 trillion including interest" and "$4.7 trillion through 2035 on a dynamic basis," sourced to two CBO publications at once. The 10 million uninsured figure was sourced only as "CBO" with no publication number, while the deficit scores already named 61570 and 61466.
Corrected to
$4.1T including interest is sourced to CBO 61466; $4.7T through 2035 on a dynamic basis is sourced to CBO 61882. The 10 million uninsured figure is sourced to CBO 61367 (August 11, 2025 coverage tables), which is now a clickable source. The $3.4T conventional score is unchanged.
How the error happened
The archive already had three CBO deficit numbers for this law. Two of them were sitting in the same box, and the 10 million uninsured figure named CBO without a link. They are now separate, and the coverage tables have a link.
Full technical detail
Invariant 9 Bin A, and the same blending defect class as the DOGE contract figures: two real, different CBO numbers in one slot. Logged per invariant 8.
Published as
statusDetail named Dobbs, Bruen, Loper Bright, and Trump v. United States as decisions of the resulting majority, but the clickable sources list had only Dobbs and the Federal Judicial Center database.
Corrected to
Added the Supreme Court PDFs for Bruen (20-843), Loper Bright (22-451), and Trump v. United States (23-939). Dobbs and the FJC database remain.
How the error happened
The entry already listed the major cases this Court decided. Only Dobbs was a link. The other three opinions are now links too.
Full technical detail
Invariant 9 Bin A: named opinions that were not clickable. Logged per invariant 8.
Published as
Overview, staples, and vs-presidents showed 54 second-term confirmations as 9 appellate and 45 district as of July 2026. The judges entry's own statusDetail already said 287 Article III judges across both terms, which is 234 + 53, so the tile contradicted the entry it sat next to.
Corrected to
53 as of August 1, 2026: 10 appellate, 42 district, 1 Court of International Trade, matching Brookings (July 31) and Ballotpedia (August 1). First-term 234 is unchanged. The tile stays non-clickable because no single entry is about this-term confirmations as a figure.
How the error happened
The front of the site said 54 new judges this term, 9 of them appellate. Independent Senate trackers and the archive's own combined total both say 53, with 10 appellate, 42 district, and one trade-court seat. The first-term 234 did not change.
Full technical detail
Invariant 9 Bin A: a count that was internally inconsistent with the archive's own 287 combined total, independently confirmed by two outside trackers. Logged per invariant 8.
Published as
An estimate said dynamic feedback offset "roughly 20% of the static cost," sourced only as "JCT macroeconomic analysis." JCX-69-17 says the conference agreement's conventional $1,456 billion revenue loss is reduced by $451 billion of growth feedback (about 31 percent), with $66 billion of extra debt service netting that to $385 billion (about 26 percent). Twenty percent is not in that paper.
Corrected to
The estimate now states JCT's published dollars and both percentages, and JCX-69-17 is a clickable source next to JCX-67-17.
How the error happened
The archive said extra growth offset about 20 percent of the 2017 tax law's cost, and attributed that to JCT. JCT's actual paper says $451 billion of feedback on a $1.46 trillion conventional score, which is about 31 percent, or about 26 percent after extra interest on the debt. The big deficit number did not change. The percentage did.
Full technical detail
Invariant 9 Bin A: a rounded figure that does not appear in the named source. Logged per invariant 8.
Published as
An estimate dated Proclamation 10989 to November 10, 2025. The proclamation is dated November 7, 2025 ("this seventh day of November"). November 10 was the news cycle. It was published in the Federal Register on November 14.
Corrected to
The estimate says November 7. The Federal Register document (2025-19928) is now a clickable source.
How the error happened
The pardon for people connected to the 2020 alternate-elector slates was signed November 7, 2025. The archive had November 10, which is when a lot of the coverage ran. Same proclamation, right date, and the Federal Register page is now a link.
Full technical detail
Invariant 9 Bin A: a real grant, dated from the press day instead of the instrument. Logged per invariant 8.
Published as
statusDetail, the apprehension estimate, Overview/now-state/staples/dossiers/vs-presidents, and Commonly Misread all still carried FactCheck.org's April 2026 vintage (85,218 apprehensions, a 92% decline) while the entry's asOf was already August 2026. The estimate named "CBP data via FactCheck.org" and a Pew FY2025 encounter analysis, but neither document was in the entry's clickable sources list.
Corrected to
Apprehension estimate and every derived rendering updated to FactCheck.org's July 2026 update: 90,875 over twelve months, about a 91% decline. Added two clickable sources: the July FactCheck update and Pew's Feb. 2, 2026 southwest-border encounter analysis (the 237,538 FY2025 figure already in the entry). The decline remains the administration's central claimed achievement; only the vintage moved.
How the error happened
The archive was still quoting an April number for border crossings after a July update existed, and clicking the entry's sources did not open the FactCheck or Pew pages the text itself named. The newer number is a bit higher (90,875, about 91% down, not 85,218 / 92%). The drop is still huge. The links now go to the actual documents.
Full technical detail
Invariant 9 Bin A: a status/asOf freeze, the dominant defect class of the 2026-08-17 sweep, plus a clickability gap. The underlying fact (a collapse in southern-border apprehensions) was never in dispute. Logged per invariant 8.
Published as
The entry's estimates cited the August 6, 2026 GAO audit (GAO-26-108615) in four places and a Lancet USAID-mortality paper in one, but the clickable sources list had only BLS and the founding executive order. The Dossiers beat and a Milestones row still used the pre-sweep blended wording ("nearly 2,000" contracts / "nearly $35 billion") that the entry itself had already replaced with GAO's two distinct figures ($27.4 billion / 2,503 contracts, and $37.0 billion / 3,910). Federal civilian employment was still quoted as 352,000 / 11.7% from FactCheck's April vintage; the July vintage is 324,000 / 10.8% through June 2026, consistent with rehiring after the freeze ended.
Corrected to
Added GAO-26-108615 and Cavalcanti et al., The Lancet (2025) as clickable sources. Dossiers and Milestones now carry the same two GAO contract/grant figures the entry already had. Employment figure and every derived rendering (Overview, now-state, staples, vs-presidents, Milestones, Dossiers) moved to the July vintage. The workforce reduction remains real; the savings ledger remains unverified.
How the error happened
Readers could not click through to the GAO audit or the Lancet paper the entry was quoting. A couple of other pages still had an old blended savings number the main entry had already split into two precise GAO figures. The federal jobs-cut count was also an April snapshot; the July figure is a bit lower because some hiring resumed after the freeze ended.
Full technical detail
Invariant 9 Bin A: a clickability gap, a leftover of a previously logged blended-figure correction that had not been swept into Dossiers/Milestones, and an asOf freeze on the employment count. Logged per invariant 8.
Published as
Estimates quoted Learning Resources, Inc. v. Trump (2026) and "up to $175 billion in refunds" from the Penn Wharton Budget Model, but the clickable sources list was CRS, the Section 122 statute, and a Holland & Knight writeup. A reader opening the entry could not open the opinion or the model that supplied the headline $175B figure.
Corrected to
Added the Supreme Court opinion PDF (24-1287, Feb. 20, 2026) and PWBM's February 20, 2026 IEEPA revenue-and-refunds note as clickable sources. The $175B figure, the 6-3 holding, and the Section 122 replacement are unchanged.
How the error happened
The entry already said the Supreme Court struck the tariffs down 6-3 and that Penn Wharton projected up to $175 billion in refunds, but clicking Sources did not open either of those documents. It does now. Nothing about the ruling or the dollar figure changed.
Full technical detail
Invariant 9 Bin A: the documents the text already named were not clickable. Logged per invariant 8.
August 17, 2026 · Jobs "so far" figures updated from the March vintage to June 2026; Claims tally source made clickableMaterial: stale figures updated; a named source made clickable
Published as
Overview, now-state, staples, and vs-presidents still showed +369,000 jobs (January 2025–March 2026) and a 14-month comparison from FactCheck.org's April update, while the archive's asOf was August 2026. The Claims view's 30,573 tally named the Washington Post Fact Checker as its source but the tile was not a link to that article; the whole card routed to Methodology.
Corrected to
Jobs figures updated to FactCheck.org's July 2026 update: +716,000 from January 2025 to June 2026 against +2,007,000 in the preceding 17 months, private sector +902,000. The Claims 30,573 source line is now a clickable link to the Post's January 24, 2021 final-count article; the number itself still opens Methodology so the counting rules stay one click away.
How the error happened
The jobs-added number on the front of the site was still the March snapshot (369,000) in August. The July snapshot is 716,000 through June, still far slower than the prior 17 months. Separately, the 30,573 false-or-misleading-claims count named the Washington Post as its source but you could not click through to the Post's article. You can now.
Full technical detail
Invariant 9 Bin A: asOf freeze on a "so far this term" figure, and a named source that was not clickable. The March window was labeled, so the old number was not false for that window; leaving it up under an August asOf is the same defect class as a frozen statusDetail. Logged per invariant 8.
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.
August 16, 2026 · 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.
August 16, 2026 · 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.
August 16, 2026 · 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.
August 16, 2026 · 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.
August 16, 2026 · 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.
August 15, 2026 · 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.
August 15, 2026 · 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.
August 15, 2026 · 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.
August 15, 2026 · 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.
August 14, 2026 · 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.
August 14, 2026 · 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.
August 14, 2026 · 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.
August 14, 2026 · 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.
August 14, 2026 · 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.
August 10, 2026 · 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.
August 10, 2026 · 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.
August 13, 2026 · 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.
August 13, 2026 · 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.
August 16, 2026 · 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.
Published as
The entry said Trump v. CASA (June 2025) left the underlying Fourteenth Amendment question undecided, and that the question remained open — accurate when written, but the entry was never updated after a later ruling.
Corrected to
Trump v. Barbara, No. 25-365 (argued April 1, 2026, decided June 30, 2026, 6-3) directly resolved the question the entry described as open, holding that children born in the US to parents unlawfully or temporarily present are citizens at birth under the Fourteenth Amendment, and striking down EO 14160. status, statusDetail, contested, and effect #2 (claim and all three estimates) updated to reflect the actual ruling, its vote, and its dissents; the opinion added as a new Tier 1 source. Also noted, without expanding this entry's scope: on August 6, 2026 the administration issued narrower follow-on orders on the same underlying policy goal, which this entry does not cover.
How the error happened
Found during an independent fact-checking pass (a research agent verified against the primary source, then re-confirmed directly by downloading and reading the actual slip opinion) ahead of sharing the site more widely. This was the single most consequential finding of that pass — a currently-live claim about a resolved Supreme Court question that was, in fact, already resolved.
Published as
status/statusDetail described a ceasefire in effect since April 8, 2026, "neither concluded nor formally resumed." The nuclear-program effect claimed no public, independently verified damage assessment existed.
Corrected to
Updated to reflect the June 17 memorandum, the June 28 ceasefire agreement, and its collapse on July 8, 2026, after which hostilities resumed. Also added that Ali Khamenei was killed in the February 28 opening strikes, noting the disputed characterization of the succession as "regime change." The nuclear-program effect was corrected: independent assessments do exist (Institute for Science and International Security satellite imagery reports; an IAEA non-compliance finding), even though they disagree with each other and with belligerents' own claims on the actual extent of damage — a materially different fact from "no assessment exists."
How the error happened
Found during an independent fact-checking pass ahead of sharing the site more widely, then independently re-verified (Wikipedia's infobox status, ISIS's own published report list). A fast-moving conflict entry going stale is expected; leaving it stale once found is not.
Published as
contested and two effect estimates stated that no public determination of the messages' classification status existed.
Corrected to
The DoD Inspector General's December 2, 2025 evaluation (Report No. DODIG-2026-021, already correctly cited in this entry's own sources) found the source document was marked classified at the time, but explicitly declined to determine whether the information as shared, or its declassification, was proper. Updated contested and both dependent estimates to state that narrower, more accurate finding rather than either "no determination" or "settled as classified" — both overstate or understate what the IG report actually says.
How the error happened
Found during an independent fact-checking pass; the entry's original framing was closer to correct than a first independent check suggested, so the fix reflects the report's actual, careful non-conclusion rather than swinging to the opposite overstatement.
Published as
contested and one effect estimate stated the administration's DOJ legal opinion had been declined for public release.
Corrected to
A redacted version of the opinion was released to Congress and the public on January 13, 2026 — roughly ten months into the operation. Updated contested and the legality effect's first estimate to state the actual release date and that redactions still limit independent evaluation, rather than describing it as withheld outright.
How the error happened
Found during an independent fact-checking pass ahead of sharing the site more widely.
Published as
summary and action stated the promises were made in the order tips, then overtime pay, then Social Security.
Corrected to
The real order was tips (June 9, 2024, Las Vegas rally), then Social Security (July 31, 2024, Truth Social post), then overtime pay (September 12, 2024, Tucson rally) — overtime was the last of the three introduced, not the second. Does not affect the standing verdict or the enacted/not-enacted analysis.
How the error happened
Found during an independent fact-checking pass ahead of sharing the site more widely — a small, specific, checkable claim that was simply wrong.
Published as
status/statusDetail said the archive recorded no final merits ruling on whether a President may remove a Fed governor at will.
Corrected to
The Supreme Court ruled 5-4 in Trump v. Cook on June 29, 2026 that the removal was unconstitutional. Independently confirmed directly against the Federal Reserve's own current board roster, which lists Cook as a sitting governor. Updated status, statusDetail, effect #2, and added the ruling as a source. Also removed from provisional.json — the case is no longer live litigation.
How the error happened
Found during a second independent fact-checking pass targeting the archive's highest-risk entries (active litigation, ongoing conflicts). Re-verified directly against the Fed's own primary source before editing.
Published as
statusDetail claimed rates rose "again in 2022-23 despite public pressure" with no source for that specific episode. The entry made no mention of Powell's chairmanship ending or the DOJ investigation into him.
Corrected to
Removed the unsupported 2022-23 pressure claim (Trump was out of office for most of that hike cycle; no source documents it). Added that Powell's term ended May 22, 2026, Kevin Warsh was confirmed as his successor (Senate 54-45, May 13, 2026), and a federal grand jury investigation into Powell produced subpoenas a federal judge acted on in March 2026 before DOJ ended the inquiry in April 2026. Re-verified directly against the Fed's own current roster and independent reporting.
How the error happened
Found during a second independent fact-checking pass. The entry's only two sources (a meeting calendar and a statutory table of contents) documented none of its own central claims — a real sourcing gap, not just staleness.
Published as
One estimate said "ICE's own account described medical distress in segregation" regarding the January 3, 2026 death of Geraldo Lunas Campos.
Corrected to
Independent reporting (KFF) states ICE characterized this death as a suicide, not medical distress. Corrected the estimate to match ICE's actual public characterization, which contrasts with the medical examiner's homicide ruling recorded in the same sentence.
How the error happened
Found during a second independent fact-checking pass; misattributing a party's own stated position, even in the party's disfavor by coincidence here, is the same accuracy standard as any other claim.
Published as
status/statusDetail asserted litigation over the 2025 withholding was ongoing.
Corrected to
Could not independently confirm active litigation exists; independent reporting describes the underlying 2025 funding gap in the past tense (a roughly nine-month closure). Rather than assert a specific alternative status also unconfirmed, softened the claim to record this as an open question.
How the error happened
Found during a second independent fact-checking pass. Two independent verification attempts on the litigation status were inconclusive rather than confirming; the honest fix is to record the uncertainty, not to guess a replacement claim.
Published as
statusDetail described only the Supreme Court's emergency-posture order permitting enforcement, with no mention of any subsequent appellate ruling.
Corrected to
Added the June 1, 2026 D.C. Circuit ruling (Talbott litigation, 2-1) holding the policy "arbitrary, and based on animus," which lets roughly 1,000 currently-serving openly transgender troops remain in service while leaving new-enlistment blocking intact. Added as a source.
How the error happened
Found during a second independent fact-checking pass; a two-and-a-half-month-old appellate ruling directly on this entry's subject, unmentioned in an entry stamped current as of the same month.
Published as
statusDetail said later-phase provisions "have not been implemented" with no mention of any intervening developments.
Corrected to
Added that Hamas announced the resignation of its own Gaza civil administration (July 6, 2026) and that a disarmament agreement was announced (July 31, 2026) with the Al-Quds Brigades consenting to it (August 2, 2026) — while still correctly noting actual disarmament and reconstruction had not occurred.
How the error happened
Found during a second independent fact-checking pass on this fast-moving entry.
Published as
statusDetail (and the same line duplicated in now-state.json) listed negotiating rounds in "Abu Dhabi, Miami."
Corrected to
The real round was in Geneva, not Miami — no independent source documents a Miami round. Fixed in both the entry and the duplicate copy in now-state.json.
How the error happened
Found during a second independent fact-checking pass, cross-checked against a detailed, dated account of the 2026 negotiating rounds.
Published as
status called the subsidy question "unresolved" while statusDetail, in the same entry, already said the subsidies "were not extended" (past tense). The GAO source URL returned a real 404.
Corrected to
status now reads "subsidies lapsed, not reinstated," matching statusDetail's own already-correct language. Fixed the GAO URL to its current path.
How the error happened
Found during a second independent fact-checking pass; an entry contradicting itself between two of its own fields is a real internal-consistency defect regardless of which claim is correct.
Published as
The affected-positions estimate said the range was "tens of thousands to over 50,000," with no mention of an actual implemented figure.
Corrected to
The June 3, 2026 implementing order actually reclassified approximately 8,000 positions (97% at GS-15+) — reported as "significantly lower than the initial estimate." Kept the original OPM range as historical context and added the real implemented number.
How the error happened
Found during a second independent fact-checking pass; the entry's own asOf date postdated the real implementation figure by two months.
Published as
The Hague Summit Declaration source linked to NATO's general official-texts index rather than the declaration itself. statusDetail did not mention Spain's carve-out from the 5% target.
Corrected to
Fixed the source to the specific, stable Hague declaration URL. Added that Spain negotiated a carve-out (roughly 2.1% rather than 5%) at the summit itself.
How the error happened
Found during a second independent fact-checking pass — the same generic-landing-page defect class found across 10 other entries earlier in this same sweep.
Published as
A CREW article from February 2025 (last updated April 2025) was cited as the source for a January 2026 bank-charter application it could not have mentioned.
Corrected to
Relabeled the source to match what it actually covers (general monetizing-the-presidency tracking) and updated the estimate's own source line to note the charter-application fact is separately, independently reported.
How the error happened
Found during a second independent fact-checking pass — the underlying fact checked out true, but the specific citation attached to it did not support it.
Published as
An estimate said 2018-2019 farm payments ($23B) exceeded the auto industry bailout in nominal terms. The GAO source URL 404'd. statusDetail asserted further aid was authorized in 2025 without citing a source for it.
Corrected to
The real TARP Automotive Industry Financing Program was $79.7B — farm payments were smaller, not larger. Corrected the comparison. Replaced the dead GAO link with the collection page and an honest provenance note. Softened the unsourced 2025-aid claim to record it as unconfirmed rather than asserted.
How the error happened
Found during a second independent fact-checking pass; the auto-bailout comparison was independently checked against Wikipedia's TARP figures and was simply wrong.
Published as
A 2024 House Oversight Committee report was labeled "majority-party staff."
Corrected to
House Republicans held the Oversight majority in the 118th Congress; the report was Oversight Democrats' minority-staff work. Corrected the lean field.
How the error happened
Found during a second independent fact-checking pass, confirmed against the live House committee composition and contemporaneous reporting on the report's authorship.
Published as
This entry independently repeated the venezuela entry's already-corrected "DOJ opinion kept classified" claim and the iranwar entry's already-corrected "ceasefire since April 8, violated" framing. summary said the two operations began "in the first six weeks of 2026" (Jan 3 to Feb 28 is eight weeks).
Corrected to
Updated both claims to match the corrections already made in the venezuela and iranwar entries (redacted opinion released Jan 13 2026; ceasefire collapsed July 8, blockade reinstated July 14). Fixed "six weeks" to "eight weeks."
How the error happened
Found during a second independent fact-checking pass, which specifically checked this entry for consistency with corrections made earlier in the same sweep — confirming that kind of drift is a real, recurring risk across entries covering the same underlying events.
Published as
The entry's "234 judges" figure was correctly scoped to the first term, but the entry made no mention that confirmations continued into the second term.
Corrected to
Added that 287 total Article III judges had been confirmed across both terms as of July 2026 — roughly 50 more since the first-term total.
How the error happened
Found during a second independent fact-checking pass; nothing in the original entry was false, but a reader could reasonably expect an "effects ongoing" entry with an August 2026 asOf date to mention the confirmations continued.
Published as
statusDetail attributed PATTERN criticism to "the DOJ's own review committee."
Corrected to
The statutory Independent Review Committee the Act requires DOJ to convene is deliberately structured to be independent of DOJ, not an internal DOJ office — the opposite institutional relationship "DOJ's own" implies. Corrected, and added that external groups including the ACLU have also raised the same criticism.
How the error happened
Found during a second independent fact-checking pass.
Published as
action said "formal UN notification August 2017; effective November 4, 2020" — internally inconsistent, since a one-year notice period from August 2017 would land around August 2018, not November 2020. A Contextual-attribution claim used "driven substantially by," sharing the root of the rule-banned "drove."
Corrected to
Clarified that August 2017 was a preliminary notice of intent, and the binding Article 28 notification (which triggers the one-year clock) could only be submitted three years after entry into force — deposited November 4, 2019, effective November 4, 2020, which is now internally consistent. Reworded "driven substantially by" to "associated substantially with."
How the error happened
Found during the full-archive fact-check sweep.
Published as
Cited the SUPPORT Act's House vote as 393-8. Cited the overdose-death peak as "above 111,000 in 2022."
Corrected to
The real House vote was 396-14. The real peak was roughly 109,600, in a 12-month rolling window ending January 2023, not within calendar year 2022 specifically.
How the error happened
Found during the full-archive fact-check sweep, independently cross-checked against Wikipedia's sourced figures.
Published as
status/statusDetail said the individual provisions, set to expire after 2025, were "extended by" OBBBA — implying a future sunset still exists.
Corrected to
OBBBA made the individual provisions permanent, the same as the corporate rate cut, not merely extended. No future sunset remains.
How the error happened
Found during the full-archive fact-check sweep. Two other flagged figures in this entry (the 65% households and 20% dynamic-offset numbers) could not be independently confirmed or refuted this session and were left unchanged rather than replaced with an equally-unconfirmed alternative.
Published as
An estimate attributed "roughly 1,000 jobs added... against an estimated 75,000 fewer jobs" directly to a named Federal Reserve working paper.
Corrected to
That paper (confirmed by reading it in full) contains only relative percentage findings, not these absolute counts. The figures themselves are a widely-cited estimate elsewhere in tariff commentary; reworded to reflect that distinction rather than over-attributing them to a source that does not contain them.
How the error happened
Found during the full-archive fact-check sweep — the same "citation supports the label but not the specific claim" defect class already logged elsewhere in this archive.
Published as
status said reunification litigation "concluded 2023." The HHS OIG source URL 404'd.
Corrected to
A settlement was court-approved in December 2023, but the underlying case remains open — courts have found continued breaches as recently as 2025, with roughly 2,000 children still unlocated as of 2024. Fixed the dead OIG link to its current URL.
How the error happened
Found during the full-archive fact-check sweep.
Published as
status/statusDetail described the 2026 joint review as "scheduled," implying it had not yet occurred.
Corrected to
The review occurred July 1, 2026 — the US declined Canada's requested 16-year renewal. The agreement remains in force but now requires mandatory annual reviews through its 2036 sunset.
How the error happened
Found during the full-archive fact-check sweep, independently re-confirmed against Wikipedia's sourced account before editing given the significance.
Published as
status/statusDetail said "regional expansion stalled."
Corrected to
Kazakhstan was announced as joining November 6, 2025 and formalized its entry in early 2026 — the first expansion into Central Asia. Somaliland separately pledged to join in December 2025. Neither appeared anywhere in the entry.
How the error happened
Found during the full-archive fact-check sweep (single-sourced by the research agent), independently re-confirmed against Wikipedia before editing given the significance.
Published as
An estimate about lost flu-surveillance access cited a source ("CDC and public health association statements") that does not appear anywhere in the entry's own sources array and could not be independently confirmed. contested did not mention WHO's own public dispute over the withdrawal's validity.
Corrected to
Reworded the flu-surveillance claim to record it as unconfirmed rather than asserted. Added that WHO has publicly questioned the withdrawal's validity under the 1948 joint resolution's unpaid-obligations condition — a real, current, separate dispute from the justification debate the entry already covered.
How the error happened
Found during the full-archive fact-check sweep.
Published as
status said "collection ceased February 22, 2026." A related entry (tariffrevenue) independently found a possible Feb 24 date elsewhere and left it unresolved.
Corrected to
February 22 was the CBP announcement date (CSMS #67834313); the actual cessation date was February 24, 2026, two days later. Fixed here and in the tariffrevenue entry's duplicate reference to the same date. Also fixed a dead uscode.house.gov citation to a working Cornell LII mirror.
How the error happened
Found during the full-archive fact-check sweep, which definitively resolved a discrepancy this same sweep had flagged but left open in an earlier round.
Published as
An estimate cited "approximately 80 miles" of net-new wall mileage to a GAO source. statusDetail described only first-term construction, with no mention of continued second-term building.
Corrected to
The cited GAO report does not contain a mileage breakdown at all; the commonly-reported independent figure is approximately 47 miles, not 80. Recorded as an open discrepancy rather than silently resolved in either direction. Added that construction continued into the second term as the "Smart Wall" program (rebranded October 2025, targeting 2027/2028 completion).
How the error happened
Found during the full-archive fact-check sweep.
Published as
A CBO citation (cbo.gov/publication/56964) was used to support a claim about CBO revising its mandate-repeal coverage model. statusDetail said California v. Texas (2021) "upheld" the ACA.
Corrected to
The cited URL actually resolves to CBO's "Final Sequestration Report for Fiscal Year 2021" — unrelated to health insurance. Replaced with the real CBO coverage-model report the underlying claim actually rests on. Corrected the case description: California v. Texas was dismissed on standing grounds without a merits ruling, not an affirmative "upholding."
How the error happened
Found during the full-archive fact-check sweep — the citation was fetched directly and read to confirm the mismatch.
Published as
An estimate said "roughly 48-50% of 317 catalogued objectives" per the crowdsourced tracker. Another estimate said the President "publicly referenced Vought's Project 2025 role approvingly in a 2025 post," citing "Truth Social posts, 2024 and 2025" with no actual post in the sources array.
Corrected to
The same live tracker now shows 211 of 321 (roughly 66%) — updated to show both figures and that the instability the entry already warns about has continued. Reworded the uncitable 2025-post claim to record it as unconfirmed.
How the error happened
Found during the full-archive fact-check sweep.
Published as
One effect claim (Direct attribution) said troops "remained active in DC, Memphis and Los Angeles" — directly contradicting this same entry's own statusDetail two fields up, which correctly says the Guard was withdrawn from Los Angeles.
Corrected to
Removed Los Angeles from the active-deployment claim, matching the entry's own correct statusDetail and the real withdrawal (upheld by the Ninth Circuit, effective December 15, 2025).
How the error happened
Found during the full-archive fact-check sweep — a real internal self-contradiction within one entry, not just staleness against the outside world.
Published as
statusDetail described the November 2025 dismissals with no mention of any subsequent challenge to them.
Corrected to
Added that DOJ appealed the dismissals to the Fourth Circuit around February 9, 2026, and that appeal remained unresolved as of this entry's verification date.
How the error happened
Found during the full-archive fact-check sweep.
Published as
action said "IEEPA collection ceased February 22, 2026" — the announcement date, not the actual cessation date.
Corrected to
Corrected to February 24, 2026, matching the same fix just made in the ieepa entry.
How the error happened
Follow-up from the same fact-check finding that resolved the ieepa entry's date.
Published as
statusDetail and contested both described the underlying birthright-citizenship constitutional question as still entirely open, four months after this archive's own birthright-citizenship entry recorded that it was resolved.
Corrected to
Added that the class actions this ruling routed litigants toward reached the Supreme Court and were decided June 30, 2026 in Trump v. Barbara, which struck down the birthright citizenship order — cross-referencing the entry that already documents this with a primary citation.
How the error happened
Found during the full-archive fact-check sweep.
Published as
statusDetail described "the February 2026 termination of the IEEPA tariffs" as removing part of the price pressure, with no mention that they were replaced.
Corrected to
Corrected to reflect that IEEPA tariffs were invalidated by a Supreme Court ruling (Learning Resources, Inc. v. Trump, Feb 20, 2026), not administratively withdrawn — and that the administration replaced them within months with Section 122 and Section 301 tariffs at broadly comparable rates, so the tariff-driven price impulse hasn't clearly receded. Matches this archive's own ieepa entry.
How the error happened
Found during the full-archive fact-check sweep.
Published as
The uscode.house.gov citation for 42 U.S.C. § 265 rendered a "Document not Found" page — missing required query parameters.
Corrected to
Added the num=0&edition=prelim parameters uscode.house.gov needs to resolve the granule; verified live that it now renders 42 USC 265.
How the error happened
Found during the full-archive fact-check sweep.
Published as
An estimate said the Court "expressly declined to consider campaign statements as evidence of purpose." statusDetail described the 2025 proclamation with no mention of subsequent litigation.
Corrected to
Corrected: the majority opinion devotes several pages to the campaign statements and holds they don't override a facially legitimate justification under rational-basis review — it did not decline to consider them. Added that the 2025 proclamation has drawn litigation, including an APA violation finding over a blanket adjudication pause and a ruling against separating asylees from family.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against the opinion text before this fix.
Published as
The only CBO source cited (cbo.gov/publication/61486) is CBO's dynamic estimate of the House-passed bill before enactment — its figures don't match the $3.4T/$4.1T/$4.7T/$5.5T cited next to it. action described the vote as simple party-line reconciliation.
Corrected to
Replaced with the three real CBO publications backing each figure (61570 for $3.4T, 61466 for $4.1T, 61882 for $4.7T). Corrected the vote to 51-50 in the Senate with VP Vance breaking a tie after three Republicans — Collins, Paul, Tillis — voted no.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by fetching all four CBO publications and the Senate roll call directly before this fix.
Published as
An estimate said "more than half — nearly $35 billion — was either not terminated or could not be corroborated... Nearly 2,000 of 13,476 contracts."
Corrected to
GAO-26-108615 gives two distinct real figures that had been blended into one invented number: $27.4B (44.9%, 2,503 contracts) with no termination action taken, and $37.0B (60.7%, 3,910 contracts) where DOGE didn't follow its own methodology. Cited both precisely instead.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by fetching the GAO report directly before this fix.
Published as
The entry referred to Todd Blanche only as "Deputy Attorney General" throughout, with no mention that Pam Bondi was fired or that Blanche became Attorney General. statusDetail said only "a federal judge ordered... The dispute is unresolved," without naming the case, judge, or its escalation.
Corrected to
Added that Bondi was fired April 2, 2026 and Blanche was confirmed and sworn in as Attorney General on August 10, 2026 (kept his January 2026 statement correctly attributed to his role at the time). Named the case (Phang v. Blanche), the judge (Emmet G. Sullivan), the June 25, 2026 preliminary injunction, and the August 13, 2026 hearing where the judge warned contempt "is not a threat. It's a promise."
How the error happened
Found during the full-archive fact-check sweep. Note: a separate flagged claim — that the "roughly half of six million documents" framing was a critic's rebuttal, not DOJ's own words — was independently checked and found to be WRONG; the entry's original attribution to Blanche himself was already correct and was left unchanged. Independent verification catching a false positive from the first research pass, not just confirming true ones.
Published as
status/statusDetail said "vaccines remain authorized and licensed" with no mention of any subsequent change.
Corrected to
On August 27, 2025, FDA revoked the Pfizer, Moderna and Novavax EUAs and narrowed approved use to people 65+ or younger people with a high-risk condition. Verified directly against FDA's own live Comirnaty product page.
How the error happened
Found during the full-archive fact-check sweep.
Published as
The CARES Act citation linked to S.3548, which shows "Introduced" only on congress.gov and never became law.
Corrected to
The CARES Act (Public Law 116-136) was actually enacted as H.R.748, a "shell bill" gutted and replaced by Senate amendment. Fixed the citation to the correct bill.
How the error happened
Found during the full-archive fact-check sweep — this archive's documented "correctly labeled, wrong document" defect class.
Published as
statusDetail mentioned only the pending state appellate appeal.
Corrected to
Added that the Second Circuit revived a separate federal-removal bid on November 6, 2025 (citing Trump v. United States immunity, remanding), still pending as of a February 4, 2026 hearing where the judge signaled skepticism.
How the error happened
Found during the full-archive fact-check sweep.
Published as
An estimate said "both chambers passed war-powers resolutions... the President vetoed them" (plural).
Corrected to
Only one joint resolution (S.J.Res. 68) passed both chambers and was vetoed. A separate House-only concurrent resolution (H.Con.Res. 83) never received a Senate vote and, as a concurrent resolution, was never subject to veto.
How the error happened
Found during the full-archive fact-check sweep.
Published as
An estimate said "PCE inflation near 4.5%."
Corrected to
Recomputing year-over-year change from FRED's own PCEPI index series shows a 2026 peak of about 4.1% (May 2026), not 4.5%. Corrected.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against FRED's raw series before this fix.
Published as
An estimate said "prior HHS Inspector General reviews had found ACIP's conflict-of-interest processes broadly functional," citing a 2009 OIG report. status said "In force" with no mention of any court action.
Corrected to
The cited 2009 OIG report actually found a "systemic lack of oversight" with 64% of 2007 conflicts unresolved — the opposite finding. Corrected the citation. Added that a federal court (American Academy of Pediatrics v. Kennedy) found the reconstitution likely violated FACA and, March 16, 2026, stayed both the new members' appointments and their votes.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by reading the actual OIG PDF and the court order before this fix.
Published as
The CBO citation (publication 61486) supporting Medicaid coverage-loss estimates is a whole-bill dynamic deficit score with no Medicaid breakdown at all.
Corrected to
Replaced with CBO publication 61837, the actual Medicaid-chapter analysis: 7.5 million more uninsured by 2034, with Georgetown CCF attributing 5.3 million of that to the work-reporting requirement specifically.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by fetching both CBO publications before this fix.
Published as
statusDetail ended at West Virginia v. EPA (2022) and said "neither rule now governs" — implying a regulatory vacuum since 2022.
Corrected to
EPA finalized new Carbon Pollution Standards in April 2024, which survived stay challenges at the D.C. Circuit and Supreme Court and governed the sector from that date. The Trump EPA proposed repealing them in June 2025; as of mid-2026 that repeal remained under OMB review, not finalized.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified via EPA and Regulations.gov before this fix.
Published as
status/statusDetail said "little activity... no commercial production has occurred" with no mention of any 2025-26 sale. One estimate said "major oil companies largely declined to bid" and cited "$1 billion in revenue" to "BLM sale results."
Corrected to
Added that BLM held the first sale under OBBBA's mandate on June 5, 2026 — 5 of 58 tracts leased for $3.74M, with genuine industry bidders for the first time. Corrected "no major oil company bid" (more precise than "largely declined") and fixed the $1B figure's real source (a CBO estimate, not BLM sale results — the actual 2021 sale total was $16.5M).
How the error happened
Found during the full-archive fact-check sweep, independently re-verified via BLM's own press release before this fix.
Published as
statusDetail described one stop-work order, reversed by a court, with no mention of anything after that.
Corrected to
A second, broader stop-work order (Dec 22, 2025) was also struck down (Jan 12, 2026, same judge). Added that BOEM has since pivoted to actively canceling existing, already-granted leases through negotiated settlements — a more severe step than withholding new ones.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified via court filings and BOEM's own site before this fix.
Published as
status said "Superseded, but its narrow reading largely prevailed," ending the story at the 2023 post-Sackett rule.
Corrected to
Added that EPA and the Army Corps proposed a new, more sweeping WOTUS rule on November 17, 2025 (eliminating the "significant nexus" test, excluding groundwater, removing interstate waters as a standalone trigger); comment period closed January 5, 2026; still pending as of mid-2026.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified via epa.gov before this fix.
Published as
An estimate said the 2025 CRA resolution "eliminated the statutory methane fee." status said "standards under renewed rescission."
Corrected to
The CRA resolution disapproved EPA's implementing rule, not the statute itself — Congress separately defunded the fee months later in OBBBA. As of mid-2026 EPA has finalized only one narrow flaring/monitoring rule (explicitly preserving the rest of the 2023-24 standards); a broader reporting-program rollback remains only proposed.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified via a CRS report and the Federal Register before this fix.
Published as
An estimate said "CBO projected roughly 3.8 million more uninsured over a decade" (read as a one-time total). action described extension efforts as simply having failed.
Corrected to
CBO's actual figure is 3.8 million as a recurring annual average (2026-2034), not a decade total — corrected to the precise year-by-year figures. Added that the House passed a bipartisan standalone three-year extension 230-196 on January 8, 2026, which has since stalled in the Senate.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified via a CBO letter and congressional vote records before this fix.
Published as
statusDetail described the effort only abstractly as "voluntary manufacturer agreements," with no mention of a named program.
Corrected to
Named TrumpRx, the federal platform that launched February 5, 2026 with manufacturer deals (Pfizer, AstraZeneca, EMD Serono, Amgen) — and added that a NYT analysis found its prices didn't consistently undercut prices in other wealthy nations.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified via trumprx.gov before this fix.
Published as
An estimate cited "CEQ and GAO timeline data" for a four-year EIS completion figure.
Corrected to
The cited GAO report (GAO-14-369) explicitly concluded reliable governmentwide timeline data does not exist. The real figures come from CEQ's own analysis, already cited elsewhere in this entry. Fixed the attribution.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by fetching GAO-14-369 directly before this fix.
Published as
The GAO citation linked to a generic CRA topic-hub page with no opinion text.
Corrected to
Replaced with the actual opinion, GAO B-337179. Also added that California and ten other states sued the day the resolutions were signed; the case remains active with no injunction issued as of early 2026.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by fetching both pages before this fix.
August 17, 2026 · Archive-wideMinor: a systemic dead-link pattern across 11 entries
Published as
Every uscode.house.gov citation using the req=granuleid: URL form (11 entries: iranwar, prosecutions, blsfiring, chevron2, natlguard, universities, fema, igfirings, impoundment, tariffrevenue, signal) rendered a "Document not Found" page — the site requires additional query parameters to resolve the granule that the original URLs omitted.
Corrected to
Added the num=0&edition=prelim parameters uscode.house.gov needs (or, for fema's chapter-level citation, confirmed the same parameter form resolves it too); verified live that all 11 now render the correct US Code text.
How the error happened
A cross-cutting pattern flagged during the full-archive fact-check sweep — found in one entry during an earlier wave (title42), then swept for archive-wide during wave 3 rather than fixed one at a time.
Published as
statusDetail described current recipients as being in "indefinite limbo" with no mention of active enforcement risk. A figure conflated the active-recipient peak with the cumulative-ever-approved total.
Corrected to
Added that DHS has taken the position since 2025 that active DACA status doesn't protect against arrest or deportation, with roughly 261 recipients detained and 86-174 deported over about ten months. Corrected the peak figure: active recipients peaked at ~699,350 (Aug. 2018), not "near 800,000" (that's the cumulative-ever-approved total).
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against DHS/congressional reporting and USCIS data before this fix.
Published as
statusDetail said "The Senate voted 68-23 to oppose the withdrawal" and status said "Partial withdrawal; forces later repositioned," describing a residual US presence.
Corrected to
The 68-23 vote was an earlier, unrelated procedural vote (Jan. 31, 2019, eight months before the withdrawal) — when the Senate had a real chance to condemn the actual withdrawal, Republicans blocked a vote entirely. Also corrected: US forces completed a full withdrawal from Syria by April 16, 2026, ending the deployment entirely.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against Senate roll-call records and 2026 reporting before this fix.
Published as
statusDetail said the Sixth Circuit vacated the 2024 restoration "applying the major questions doctrine."
Corrected to
The actual January 2, 2025 opinion rests on ordinary statutory interpretation after Loper Bright ended Chevron deference, and explicitly declined to reach the major questions doctrine — which appeared only in an earlier, separate interim stay order.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by reading the opinion text before this fix.
Published as
The title and summary promise "clemency for political allies, campaign donors and convicted fraudsters," but the entry body covered only the January 2025 J6 pardons.
Corrected to
Added the second-term clemency pattern the entry's own framing describes: the November 2025 pardon of 77 people in the "fake electors" plot (including Giuliani and Meadows), and named grants to Rod Blagojevich, the Chrisleys, and Ross Ulbricht.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against contemporaneous reporting before this fix.
Published as
status said the joint venture was "announced" and statusDetail described it as still being negotiated.
Corrected to
The joint venture (TikTok USDS Joint Venture LLC) actually closed January 22, 2026 — Oracle, Silver Lake and MGX each ~15%, ByteDance retaining 19.9%. Noted that whether this satisfies the statute's "qualified divestiture" standard remains untested.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified before this fix.
Published as
statusDetail described the law as static with no mention of any 2025-26 developments.
Corrected to
Added that the Ninth Circuit held in Feb. 2025 (AIMS v. DEA) that the Act doesn't exempt Schedule I substances from CSA restrictions, and that an April 2026 executive order (EO 14401) directed FDA/DEA to build a psychedelics-specific Right to Try pathway anyway, through CSA waiver authority.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by reading the opinion and the EO text before this fix.
Published as
status said "Enjoined and vacated" with no mention of any appeal.
Corrected to
The First Circuit affirmed on January 5, 2026, and the administration's Supreme Court cert window lapsed without action in April 2026 — the litigation is concluded, not just enjoined at the district level.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by reading the appellate opinion before this fix.
Published as
The citation pointed at 29 U.S.C. § 2 (the Bureau's general statistics duty), not the Commissioner appointment/tenure provision. statusDetail said nothing about who has held the role since.
Corrected to
Fixed the citation to 29 U.S.C. § 3. Added that the next nominee's (Antoni) nomination was withdrawn in Sept. 2025, a deputy served as acting commissioner for about a year, and Brett Matsumoto was confirmed August 7, 2026.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against Cornell LII and confirmation reporting before this fix.
Published as
action described the April 9, 2025 sunset-provisions directive as a "memorandum" and cited no source for either April 9 action.
Corrected to
The sunset-provisions directive is actually a separate Executive Order (14270), distinct from the same-day repeal-without-comment memorandum. Added EO 14270 as a source.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against the Federal Register text before this fix.
Published as
The CBO citation (publication 59720) supporting claims about the 2025 IRS enforcement clawback is actually a Nov. 2023 letter scoring an unrelated $14.3B rescission tied to a 2024 Israel-aid supplemental.
Corrected to
Replaced with CBO's actual H.R. 1968 cost estimate (the 2025 vehicle that clawed back IRS funding) and CBO's own methodological report on IRS funding and revenue. Also softened an overstated taxpayer-service claim to match the mixed 2026 record.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by fetching all cited CBO publications before this fix.
Published as
statusDetail implied Washington, LA, Chicago and Portland all had ongoing deployments.
Corrected to
LA, Chicago and Portland deployments all wound down by February 2026 (Chicago after the Supreme Court declined to lift the block, Dec. 23, 2025). Added the two omitted, actually-ongoing deployments: Memphis (since Oct. 2025) and New Orleans (since Dec. 2025, extended through mid-2026).
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against court filings and 2026 reporting before this fix.
Published as
statusDetail said "No Supreme Court ruling has resolved the question" with no mention of a real stay favoring the administration. A citation said Train v. City of New York "rejected" the administration's Article II argument.
Corrected to
Added the Sept. 26, 2025 Supreme Court stay in Department of State v. AIDS Vaccine Advocacy Coalition, which lets a ~$4B foreign-aid withholding stand in practice. Corrected Train v. New York: it was decided on statutory grounds and explicitly avoided the constitutional question this dispute turns on.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against the actual ruling and Train's holding before this fix.
Published as
statusDetail said a court "ordered access restored; compliance has been partial" — framing it as a compliance shortfall against a standing order.
Corrected to
The D.C. Circuit stayed that order for the Oval Office, Air Force One, Cabinet Room and Mar-a-Lago (June 6, 2025), upholding it only for the East Room; the case remains pending with no merits ruling as of mid-2026 — the appeals court has so far sided with the administration on most locations.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against the case history before this fix.
Published as
statusDetail described transfers of function as "announced and litigated" with no mention of how the central RIF litigation actually resolved.
Corrected to
Added that the Supreme Court granted an emergency stay 6-3 in McMahon v. New York (July 14, 2025), allowing the department's workforce RIF to proceed after lower courts had blocked it.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against the ruling before this fix.
Published as
An estimate said the replacement AI order "relies on voluntary commitments and sector-specific agency authority." status said state preemption simply "failed."
Corrected to
EO 14179's actual text contains no such language — it only revokes EO 14110 and orders an AI Action Plan. Added that a December 2025 executive order (EO 14365) revived federal AI preemption efforts at the agency level after Congress stripped a similar provision in July 2025.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified by reading the EO text before this fix.
Published as
status said "Struck down — every order litigated was invalidated" and contested called the outcome "four for four against the government," with no mention of any appeal.
Corrected to
All four rulings are under active D.C. Circuit appeal, consolidated for oral argument May 14, 2026, with no ruling as of mid-August 2026 — the district-court wins stand for now but aren't final.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against the appellate docket before this fix.
Published as
statusDetail said prices remained "near record levels."
Corrected to
FHFA's House Price Index hit an all-time high in May 2026 — the highest reading since the index began in 1991. Corrected to "at or above record levels."
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against FHFA data before this fix.
Published as
statusDetail said "Portions remain in litigation" with no mention of a follow-on order or its status.
Corrected to
Added that a related later order (EO 14399, March 31, 2026) continued the same push, and that DOJ asked the Supreme Court to stay related injunctions on an emergency basis, renewing the request around August 12, 2026 ahead of the November 2026 midterms.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified before this fix.
Published as
An estimate said FEMA "lost roughly a third of permanent staff."
Corrected to
GAO's own August 2026 review puts it at about 4,300 of roughly 25,000 staff — about 17%, not a third. Corrected and re-sourced to the GAO report directly.
How the error happened
Found during the full-archive fact-check sweep, independently re-verified against the GAO report before this fix.
Published as
An estimate said the November 2025 grant pardoned 77 people "involved in" the fake-electors plot, and grouped them under a claim label calling the whole set "people convicted of fraud."
Corrected to
Per the pardon proclamation itself and contemporaneous reporting, the 77 were only ever alleged to be involved, and none were facing federal charges at the time of the pardon (a fact the proclamation and its own coverage state explicitly). Reworded to "alleged to have been involved," added that none were federally charged, and split the claim label so it no longer implies fraud convictions for people who were never charged with anything.
How the error happened
Found during a legal-posture review — this is the same overstatement invariant 9 exists to catch, applied to named individuals other than the article's subject rather than the subject himself.

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.

100 researched, sourced entries — this is the real archive, not sample dataEvery claim traceable to a primary document or a named estimateCorrections logged publicly, never silently editedNo scores. No rankings. Color marks factual standing only.An independent archive, free to read and free to reuse. No company, no funding, one anonymous maintainer. Full disclosure →Found an error? Submit a correction →
Take the data and check us
Full entry set with standing, attribution levels and every estimate. If you can rebuild this and reach a different conclusion, that is the point.