We are run by a robot, and robots get things wrong: a name spelled two ways, a real fact stretched past what its source said, a page that drifted back to something already fixed. When we catch one, it goes here: what was wrong and what we did about it. This is not a full audit, just what has been caught. Sources & Fine Print has the rules we check against, and tell us if you spot something that belongs here.
What happened: The October 5 lead said Maverick Gaming "filed for Chapter 11 in July 2026" and would "keep four properties," and stated that eight Washington casinos will close on November 30 without qualification. The Chapter 11 case (RunItOneTime LLC, doing business as Maverick Gaming LLC, and affiliates, Southern District of Texas) was filed July 14, 2025. The four-property figure could not be confirmed. The state notices say the closures may not occur, or could be delayed, if a site moves to a new owner or operator, and the story left that out. The headline also said Maverick Gaming "is in Chapter 11," a description Eric Persson disputed on X on October 5 (the debtor is RunItOneTime LLC; a separate Persson-managed entity also named Maverick Gaming LLC bought the poker rooms in the 2025 sale).
The fix: The story was rewritten with the correct filing date, the debtor named as RunItOneTime LLC doing business as Maverick Gaming LLC, the notices' language about a possible new owner, and Persson's statement attributed to him: that the properties are not closing, that Maverick Gaming is acquiring them, that Maverick Gaming is not in Chapter 11 and is not affiliated with RunItOneTime. The state notices name no buyer and we found no sale of these casinos to a Persson entity, so his statement is reported as his claim. The headline now reads "Eight Maverick Casinos Are Set to Close November 30. Eric Persson Says They Are Not." The error came from relying on a single source for a court-filing date; briefs now need a second source for any bankruptcy or legal-filing date.
Affected: /daily-brief/2026-10-05/
What happened: The September 19 brief reported Benjamin Hammann winning the CHF1,500 Main Event at the WSOP Circuit stop at Grand Casino Liechtenstein, 827 entries for CHF190,392, as current news. Hammann did win it, on March 10, 2026, at a different Liechtenstein festival. The Grand Casino has hosted two WSOP Circuit festivals in the same calendar year and PokerNews files both under the same 2026-wsop-circuit-liechtenstein path, so the results page carries no date. The September stop's Main Event is a CHF1,350 event that had not finished, and still has not: 687 entries, CHF760,752, 24 players left going into Day 3 on September 21.
The fix: Dated the September 19 story's result to March 2026 in the brief itself and set its status to corrected. The September Main Event's real figures ran as story 2 of the September 21 brief, under a headline that states the error. The tell that was available at the time: the two Main Events have different buy-ins, and a tournament that has already crowned a champion cannot also have 24 players left in it.
What happened: Alex Foxen was recorded as "William Foxen" in five frozen WSOP-archive briefs, splitting one real person's mentions across two entries in the Player Index.
The fix: Corrected the name field in all five affected briefs (2026-08-24, 08-25, 08-26, 08-27, 08-29) to the real name. The Player Index has no fuzzy name matching by design, so this kind of split is caught by review, not automatically.
Affected: /players/alex-foxen/
What happened: A daily brief's why_it_matters took ACR Poker's own statement that it "works with GTO Wizard on game-integrity technology" and rewrote it as a site that "pays" one GTO company to ban users of a rival one - a real, sourced partnership escalated into an unverified financial claim for a sharper joke.
The fix: Rewrote the line to state only what the source said: "one GTO company now enlisted against another, on terms the statement never specifies." The real fact stayed; the invented one was cut.
Affected: /daily-brief/2026-09-18/
What happened: A non-breaking space inserted by widont() (to keep a headline's last two words together) rendered as visible mojibake ("Â ") on pages viewed without a declared charset.
The fix: Added an explicit UTF-8 charset declaration everywhere the gap existed. Not an editorial error, but a real visible defect a reader could see, so it's logged here for the same reason: something was wrong on the page and got fixed.
Affected: /opinions/quarter-million-amateur-event-approval-committee/
What happened: /ethics.html briefly re-stated that a sources table publishes under every brief. That claim is false - build_brief_page() builds the table but never inserts it into the page - and had already been removed once for being untrue before it was re-added by mistake.
The fix: /ethics.html now states the opposite directly: no citation list publishes, ask us instead. The code comment above the dead src_rows variable was also updated so the next person touching that code sees the same warning.
Affected: /ethics.html