Skip to content
Hugin
Hugin / Public record

Source ledger

This desk keeps saying that coverage is not the record. That only means something if we can reach the records. So we tried to read every one we cite, and this is the result — including the parts that did not work.

591 records cited88.9% retrieved by an automated readReachability JSON

Looking for local officials? See the state-by-state coverage and gaps for councils, county boards and school boards, including missing rosters, contacts and unverified election seats.

Read this the right way. A failed read is a fact about Hugin, not about a publisher. When a server declines an automated request it is running ordinary bot filtering; that implies nothing about whether the record is public to a person, accurate, or intact, and nothing about anyone’s intent. The one line here that should change how you treat a citation is not at the address we cited — and that is the queue this desk works from.

Records cited591636 citations across the case files
Retrieved by an automated read51988.9% of the 584 we checked
Declined our automated request29A limit on this desk, not a finding
Gone from the address we cited2The only reader-actionable number here

Do the records still say what we cite them for?

Retrieving a record and confirming it still contains the fact are different things. A page can answer for years while its contents are rewritten underneath, and a citation can be wrong from the day it was written, because nothing in an ordinary editorial process ever re-opens the document to check that a figure came out of it.

So each cited fact carrying a checkable value — a sum of money, a legal citation, a docket number, a dated event — is looked for in the retrieved document itself. 590 of 750 were found. A further 105 could not be checked at all, because the source refused an automated request or the value is one this desk derived rather than quoted. That is not a pass, and it is counted separately for exactly that reason: the share confirmed of what could be tested is 91%.

Claims that need work16021.3% of 750 examined
Cited value not found34Read the passage or file a correction
Only partly found21The citation or fingerprint needs narrowing
Could not be tested105Uncertainty, kept out of the pass column

This is the verification-debt queue: 160 named facts across 11 case files and 90 source URLs, routed to the work that could clear them. Today’s verifier recovered 11 documents through an independently implemented second client after the first one was refused. 22 additional anchors remain outside fact-level checking because both clients were declined.

One instrument still disagrees with another. 3 facts are tied to a URL the source ledger read but the fact verifier could not. The conflict is published on the row; neither reading gets to erase the other.

What this check cannot do

  • Absence of a token is evidence the citation may be wrong; it is not proof. A document may state the same fact in words this tool cannot match.
  • Sources that block automated requests are skipped entirely and are listed as such, not counted as verified.
  • A 401, 403, or 429 from one HTTP client is retried with an independently implemented curl request using the same identifying user-agent. A refusal is recorded only when both clients fail.
  • Only facts carrying a checkable token are examined. A purely qualitative extracted fact cannot be verified this way and is not counted either way.
  • This checks VALUES, not propositions. It confirms a figure appears in the document; it cannot tell whether the figure is attached to the same subject. On 2026-08-05 a claim about unnamed banks reporting $170 million late was marked confirmed because the document did contain '$170 million' — describing an individual's payments to Epstein, an entirely different fact. A confirmed value is not a confirmed sentence, and only a person reading the source can close that gap.

The named queue

Ordered by what can affect a citation first: values not found, partial matches, then facts the instrument could not safely test. Open a lane to see every row and its next action.

Citation review 55

The document was in hand, but one or more cited values were not matched. This may be a bad citation, an over-broad fingerprint, or a real correction.

  1. support.claude.comValue not found
    https://support.claude.com/en/articles/15424964-claude-fable-5-promotional-access
    The article says the Fable 5 promotion is extended through July 12, 2026 at 11:59:59 PM PT.
    Looked for: July 12, 2026Source ledger: redirectedai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  2. platform.claude.comValue not found
    https://platform.claude.com/docs/en/about-claude/model-deprecations
    The row reads claude-sonnet-4-5-20250929, Active, N/A, Not sooner than September 29, 2026.
    Looked for: September 29, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  3. ai.google.devValue not found
    https://ai.google.dev/gemini-api/docs/deprecations
    The gemini-2.5-flash-image row lists a shutdown date of October 2, 2026.
    Looked for: October 2, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  4. ai.google.devValue not found
    https://ai.google.dev/gemini-api/docs/deprecations
    The image table reads: gemini-2.5-flash-image, October 2, 2025, March 15, 2027, replacement gemini-3.1-flash-lite-image. The same row read October 2, 2026 with replacement gemini-3.1-flash-image-preview when this desk read the page on 2026-09-27.
    Looked for: October 2, 2025, March 15, 2027, October 2, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  5. ai.google.devValue not found
    https://ai.google.dev/gemini-api/docs/deprecations
    The preview row below it reads: gemini-3.1-flash-image-preview, February 26, 2026, June 25, 2026, replacement gemini-nano-banana-2.1.
    Looked for: February 26, 2026, June 25, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  6. x.comValue not found
    https://x.com/OpenAI/status/2074704958419792299
    The post points to Thursday, July 9, 2026 as the public-launch date from the July 8 receipt window.
    Looked for: July 9, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  7. docs.x.aiValue not found
    https://docs.x.ai/developers/release-notes
    The page footer reads 'Last updated: September 28, 2026'.
    Looked for: September 28, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  8. oig.dot.govValue not found
    https://www.oig.dot.gov/library-item/47267
    The OIG made 4 recommendations; FAA "concurred with our four recommendations", and the OIG considers them "resolved but open pending completion of the planned actions." The FAA's response plans to complete recommendation 2 by November 30, 2026 and recommendations 1, 3 and 4 by May 31, 2027.
    Looked for: November 30, 2026, May 31, 2027Source ledger: readboeing-faa-safety-oversight

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  9. oig.dot.govValue not found
    https://www.oig.dot.gov/library-item/47267
    Appendix B prints a May 22, 2026 response from the Allied Pilots Association stating that manufacturer discussions "point to an undetermined implementation date at some point in 2028" for the software modification the report said was expected in 2026.
    Looked for: May 22, 2026Source ledger: readboeing-faa-safety-oversight

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  10. federalregister.govValue not found
    https://www.federalregister.gov/documents/full_text/text/2026/10/19/2026-21348.txt
    The Federal Register's API record for the same document number reports '"citation":"91 FR 65967"', '"publication_date":"2026-10-19"', '"effective_on":"2026-10-19"' and '"comments_close_on":null'.
    Looked for: 91 FR 65967Source ledger: readconsumer-protection-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  11. public-inspection.federalregister.govValue not found
    https://public-inspection.federalregister.gov/2026-20888.pdf
    The Register's documents record for 2026-20888 lists type 'Proposed Rule', publication_date 2026-10-13, citation 91 FR 64811, comments_close_on 2026-12-14 and dates 'Comments must be received on or before December 14, 2026.'
    Looked for: 91 FR 64811, December 14, 2026Source ledger: readcrypto-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  12. sec.govValue not found
    https://www.sec.gov/newsroom/press-releases/2026-76-sec-proposes-new-regulation-crypto-assets
    The Federal Register API lists document 2026-17183, citation 91 FR 54510, published 2026-08-21, with comments_close_on 2026-10-20.
    Looked for: 91 FR 54510Source ledger: readcrypto-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  13. oig.justice.govValue not found
    https://oig.justice.gov/reports/investigation-and-review-federal-bureau-prisons-custody-care-and-supervision-jeffrey
    The report states the Office of the Chief Medical Examiner, City of New York determined Epstein had died by suicide, and that the August 11, 2019 autopsy found "the cause of death was hanging and the manner of death was suicide."
    Looked for: August 11, 2019Source ledger: readepstein-public-records

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  14. nmdoj.govValue not found
    https://nmdoj.gov/press-release/statement-from-new-mexico-department-of-justice-spokesperson-regarding-todays-search-of-the-former-zorro-ranch/
    The statement says the search was part of the investigation announced on February 19, 2026.
    Looked for: February 19, 2026Source ledger: readepstein-public-records

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  15. america.govValue not found
    https://america.gov/privacy-policy
    The page reads: 'Last updated: September 29, 2026'.
    Looked for: September 29, 2026Source ledger: readfederal-ai-procurement-watch

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  16. govinfo.govValue not found
    https://www.govinfo.gov/content/pkg/FR-2026-10-02/pdf/2026-20319.pdf
    The Federal Register API record for 2026-20319 gives executive_order_number '14432', citation '91 FR 63121', start_page 63121, end_page 63123, signing_date 2026-09-29 and publication_date 2026-10-02.
    Looked for: 91 FR 63121Source ledger: readfederal-ai-procurement-watch

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  17. govinfo.govValue not found
    https://www.govinfo.gov/content/pkg/FR-2026-10-02/pdf/2026-20319.pdf
    The Federal Register API record for 2026-20319 gives executive_order_number '14432', citation '91 FR 63121', start_page 63121, end_page 63123, signing_date 2026-09-29 and publication_date 2026-10-02.
    Looked for: 91 FR 63121Source ledger: readfederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  18. govinfo.govValue not found
    https://www.govinfo.gov/content/pkg/FR-2026-10-02/pdf/2026-20321.pdf
    The Federal Register API record for 2026-20321 gives executive_order_number '14434', citation '91 FR 63129', start_page 63129, end_page 63130, signing_date 2026-09-29, publication_date 2026-10-02 and an empty corrections list.
    Looked for: 91 FR 63129Source ledger: readfederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  19. whitehouse.govValue not found
    https://www.whitehouse.gov/wp-content/uploads/2025/07/Americas-AI-Action-Plan.pdf
    It was released on July 23, 2025 under the subtitle Winning the Race.
    Looked for: July 23, 2025Source ledger: readfederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  20. gao.govValue not found
    https://www.gao.gov/products/gao-27-108176
    On restitution in the 21 criminal cases it states courts 'ordered restitution to IRS in response to 19 cases, for a total of over $20 million', ordered taxpayer restitution 'in response to three cases, for a total of almost $16,000', and in one case ordered two co-defendants to pay nearly $62,000 to the Iowa Workforce Development.
    Looked for: $20 million, $16,000, $62,000Source ledger: readgao-federal-improper-payments-fy2025

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  21. federalregister.govValue not found
    https://www.federalregister.gov/documents/2026/09/16/2026-18978/federal-state-unemployment-compensation-uc-program-data-availability
    The rule is effective November 16, 2026; states that need to amend their laws must do so no later than September 16, 2027.
    Looked for: November 16, 2026, September 16, 2027Source ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  22. federalregister.govValue not found
    https://www.federalregister.gov/documents/2026/09/16/2026-18978/federal-state-unemployment-compensation-uc-program-data-availability
    The rule cites DOL-OIG's identification of $45.6 billion in potentially fraudulent benefits paid in six high-risk areas and an estimated $191 billion in pandemic-period UC benefits that may have been paid improperly, 'with a significant portion attributable to fraud.'
    Looked for: $45.6 billion, $191 billionSource ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  23. pandemicoversight.govValue not found
    https://www.pandemicoversight.gov/
    As of January 2026 the PRAC supported partners in more than 1,200 pandemic-related investigations involving over 24,000 subjects and about $2.5 billion in estimated fraud loss.
    Looked for: $2.5 billionSource ledger: readpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  24. pandemicoversight.govValue not found
    https://www.pandemicoversight.gov/oversight/semiannual-reports-to-congress/october-2025-march-2026
    The report states that on November 21 and December 18, 2025 the co-founders of a PPP lender service provider were sentenced and ordered to pay over $65 million in combined restitution.
    Looked for: $65 million, December 18, 2025Source ledger: readpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  25. sba.govValue not found
    https://sba.gov/article/2025/06/23/founder-lender-service-provider-convicted-role-multimillion-dollar-ppp-fraud-scheme
    The venue was the U.S. District Court for the Northern District of Texas; sentencing was scheduled for October 10, 2025, with maximum exposure up to 20 years.
    Looked for: October 10, 2025Source ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  26. federalregister.govValue not found
    https://www.federalregister.gov/documents/full_text/text/2026/10/19/2026-21320.txt
    The Federal Register's API record for the same document number reports '"citation":"91 FR 65924"', '"publication_date":"2026-10-19"', '"effective_on":"2026-11-18"' and '"comments_close_on":null'.
    Looked for: 91 FR 65924Source ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  27. gao.govValue not found
    https://www.gao.gov/products/gao-26-108174
    Its Table 1 gives obligations for October 1, 2024 through July 2, 2025 of $295.0 billion (contracts from agencies on GAO's High-Risk List for contracting), $177.9 billion (set-aside contracts), $102.6 billion (limited liability companies and partnerships), $15.4 billion (contracts to foreign-owned businesses) and $8.5 billion (financial assistance to foreign entities), and notes: 'The risk categories above are not mutually exclusive and should not be totaled.'
    Looked for: $295.0 billion, $177.9 billion, $102.6 billion, $15.4 billion, $8.5 billion, October 1, 2024, July 2, 2025Source ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  28. gao.govValue not found
    https://www.gao.gov/products/gao-26-108663
    Public Law 119-21 provided ICE $45 billion for detention capacity through fiscal year 2029; ICE's fiscal year 2025 appropriation for detention facilities totaled around $3.8 billion.
    Looked for: $45 billion, $3.8 billion, Public Law 119-21Source ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  29. gao.govValue not found
    https://www.gao.gov/products/gao-26-108663
    ICE's average daily detained population rose from 39,314 on January 20, 2025 to 67,180 on July 30, 2026, an increase of 71 percent, and authorized detention facilities roughly doubled from 134 to 272 on July 23, 2026.
    Looked for: January 20, 2025, July 30, 2026, July 23, 2026, 71 percentSource ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  30. gao.govValue not found
    https://www.gao.gov/products/gao-26-108663
    ICE reported spending $7.7 million on nonrecoverable costs to purchase the seven warehouses it intends to sell and estimates it has spent approximately $12.8 million, as of August 2026, on utilities, security, and other services at them; GAO states a sale below ICE's $707 million purchase price will result in additional waste.
    Looked for: $7.7 million, $12.8 million, $707 millionSource ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  31. gao.govValue not found
    https://www.gao.gov/products/gao-26-108663
    ICE obligated $113 million and $313 million for renovations of warehouses in Hagerstown, Maryland and Surprise, Arizona; as of September 2026 the plans are largely on hold due to legal challenges brought by the Maryland and Arizona Attorneys General.
    Looked for: $113 million, $313 millionSource ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  32. gao.govValue not found
    https://www.gao.gov/products/gao-26-108663
    ICE paid about $7.1 million for meals it did not need at Camp East Montana from October 1, 2025 through March 12, 2026.
    Looked for: $7.1 million, October 1, 2025, March 12, 2026Source ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  33. gao.govValue not found
    https://www.gao.gov/products/gao-26-109097
    In fiscal year 2025, DHS, through seven components, obligated over $32 billion for grants and cooperative agreements.
    Looked for: $32 billionSource ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  34. gao.govValue not found
    https://www.gao.gov/products/gao-27-108853
    Its endnote 4 states that as of July 2026 'CMS onboarded 24 of the 30 planned staff members for the Office of Rural Health Transformation', funded from the $200 million OBBBA appropriated to CMS to implement the program.
    Looked for: $200 millionSource ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  35. platform.claude.comPartly found
    https://platform.claude.com/docs/en/about-claude/pricing
    Sonnet 5 introductory API pricing of $2/$10 per MTok is stated as in effect through August 31, 2026.
    Looked for: August 31, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  36. platform.claude.comPartly found
    https://platform.claude.com/docs/en/about-claude/pricing
    Standard pricing of $3/$15 per MTok is stated to take effect September 1, 2026.
    Looked for: September 1, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  37. docs.cloud.google.comPartly found
    https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions
    Rows read in that table, both retirements still ahead: gemini-3.7-flash (release date August 13, 2026) is scheduled to retire January 28, 2027, replacement gemini-3.8-flash; gemini-3.6-flash (July 21, 2026) is scheduled to retire November 19, 2026, replacement gemini-3.8-flash.
    Looked for: August 13, 2026, January 28, 2027, July 21, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  38. docs.cloud.google.comPartly found
    https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions
    The same table lists gemini-3.8-flash-cyber (September 16, 2026), gemini-3.8-flash (September 2, 2026) and gemini-nano-banana-2.1 (October 6, 2026) with no retirement date announced.
    Looked for: October 6, 2026Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  39. ai.google.devPartly found
    https://ai.google.dev/gemini-api/docs/deprecations
    Five preview rows carry a shutdown scheduled for November 17, 2026, which is still ahead: gemini-3.1-flash-tts-preview (release date February 26, 2026), replacement gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts; gemini-3.1-flash-live-preview (March 11, 2026), replacement gemini-3.8-live; gemini-2.5-flash-native-audio-preview-12-2025 (December 12, 2025), replacement gemini-3.8-live; gemini-2.5-flash-preview-tts (May 20, 2025), replacement gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts; gemini-2.5-pro-preview-tts (May 20, 2025), replacement gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts.
    Looked for: February 26, 2026, March 11, 2026, December 12, 2025, May 20, 2025, May 20, 2025Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  40. developers.openai.comPartly found
    https://developers.openai.com/api/docs/pricing
    Long-context rates for the same models are listed separately at $10.00/$45.00, $4.00/$18.00 and $0.40/$1.80.
    Looked for: $1.80Source ledger: readai-release-receipts

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  41. ftc.govPartly found
    https://www.ftc.gov/system/files/ftc_gov/pdf/StipulatedOrder-FFL.pdf
    The $1.2 million FFL payment and the $650,000 PFG payment total $1.85 million; the PFG judgment has a separate face value.
    Looked for: $650,000, $1.85 millionSource ledger: readconsumer-protection-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  42. storage.courtlistener.comPartly found
    https://storage.courtlistener.com/recap/gov.uscourts.cadc.43517/gov.uscourts.cadc.43517.01208891196.0.pdf
    The D.C. Circuit docket lists on September 21, 2026: "CLERK'S ORDER [2194153] filed consolidating cases in 26-5334 (Consolidation started 09/21/2026) with 26-5299" (order PDF: https://storage.courtlistener.com/recap/gov.uscourts.cadc.43517/gov.uscourts.cadc.43517.01208890202.0.pdf).
    Looked for: September 21, 2026Source ledger: readepstein-public-records

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  43. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/PLAW-119publ38/pdf/PLAW-119publ38.pdf
    The Act is Public Law 119-38 and was enacted on November 19, 2025.
    Looked for: Public Law 119-38Source ledger: readepstein-public-records

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  44. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/FR-2025-07-28/pdf/2025-14217.pdf
    It was published in the Federal Register of July 28, 2025 at 90 FR 35389, document number 2025-14217.
    Looked for: 90 FR 35389Source ledger: unreachablefederal-ai-procurement-watch

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  45. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/FR-2023-11-01/pdf/2023-24283.pdf
    It was signed on October 30, 2023 by President Joseph R. Biden Jr. and published in the Federal Register on November 1, 2023 at 88 FR 75191 (FR Doc 2023-24283).
    Looked for: 88 FR 75191Source ledger: readfederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  46. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/FR-2025-01-28/pdf/2025-01901.pdf
    It was published in the Federal Register on January 28, 2025 (90 FR 8237).
    Looked for: 90 FR 8237Source ledger: readfederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  47. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/FR-2025-01-31/pdf/2025-02172.pdf
    It was signed on January 23, 2025 by President Donald J. Trump and published in the Federal Register on January 31, 2025 at 90 FR 8741 (FR Doc 2025-02172).
    Looked for: 90 FR 8741Source ledger: readfederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  48. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/FR-2026-06-05/pdf/2026-11415.pdf
    It was printed in the Federal Register of June 5, 2026 (Vol. 91, No. 108) at 91 FR 34565, FR Doc 2026-11415.
    Looked for: 91 FR 34565Source ledger: unreachablefederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  49. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/FR-2024-10-03/pdf/2024-22767.pdf
    Published October 3, 2024 at 89 FR 80565, document number 2024-22767.
    Looked for: 89 FR 80565Source ledger: readfederal-ai-safety-governance

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  50. gao.govPartly found
    https://www.gao.gov/products/gao-25-107753
    About 75 percent ($121 billion) of the fiscal year 2024 total was concentrated in five program areas, including HHS's Medicare, comprising three programs ($54 billion), and HHS's Medicaid ($31 billion).
    Looked for: $54 billion, $31 billionSource ledger: readgao-federal-improper-payments-fy2025

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  51. pandemicoversight.govPartly found
    https://www.pandemicoversight.gov/oversight/semiannual-reports-to-congress/april-2025-september-2025
    The report states that in July 2025 the One Big Beautiful Bill Act (Public Law 119-21) extended the PRAC sunset date until September 30, 2034, expanded its jurisdiction to programs funded in the bill, and provided $88 million in funding.
    Looked for: $88 millionSource ledger: readpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  52. sba.govPartly found
    https://www.sba.gov/document/report-protecting-integrity-pandemic-relief-programs
    SBA states that further investigation of flagged loans is expected to identify $36 billion of pandemic relief emergency program funds that were likely obtained fraudulently, which it describes as 3 percent of the $1.2 trillion disbursed.
    Looked for: $36 billion, 3 percentSource ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  53. sba.govPartly found
    https://www.sba.gov/document/report-protecting-integrity-pandemic-relief-programs
    The estimate spans four programs, PPP, COVID-EIDL, the Restaurant Revitalization Fund, and the Shuttered Venue Operators Grant Program, and SBA attributes $31 billion, or 86 percent, to applications originating in 2020.
    Looked for: $31 billionSource ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  54. gao.govPartly found
    https://www.gao.gov/products/gao-27-108853
    It states: 'At the end of 2025, CMS awarded a total of $10 billion in RHT program funding to 50 states. The first allotment of state funding ranged from $147 million for New Jersey to $281 million for Texas.' Each state received $100 million in baseline funding, an equal share of $5 billion, with the remainder awarded as workload funding scored on rural characteristics and a technical score.
    Looked for: $100 million, $5 billionSource ledger: readpublic-spending-misuse-review

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

  55. govinfo.govPartly found
    https://www.govinfo.gov/content/pkg/PLAW-112publ105/pdf/PLAW-112publ105.pdf
    The Act is Public Law 112-105, enacted April 4, 2012 from S. 2038, and printed at 126 Stat. 291.
    Looked for: Public Law 112-105Source ledger: readstock-act-news-correlation

    Next: Read the cited passage. If the value is absent, narrow or replace the citation and file a correction; if it is present in an unmatched form, strengthen the fingerprint.

Source recovery 3

The cited address no longer produced the document. The claim rests on the reading taken when it was anchored until a stable copy is found.

  1. support.claude.comCould not test
    https://support.claude.com/en/articles/15400594-claude-cowork-june-2026-usage-promotion
    The article states the doubled Cowork usage-limit promotion now runs through August 19, 2026.
    Verifier: http-404Source ledger: not-foundai-release-receipts

    Next: Locate an official replacement, court copy, or archived version; keep the original URL and the recovery trail visible.

  2. support.claude.comCould not test
    https://support.claude.com/en/articles/15400594-claude-cowork-june-2026-usage-promotion
    Its terms state the offer is valid from June 5, 2026 through August 19, 2026 at 11:59 PM PT.
    Verifier: http-404Source ledger: not-foundai-release-receipts

    Next: Locate an official replacement, court copy, or archived version; keep the original URL and the recovery trail visible.

  3. support.claude.comCould not test
    https://support.claude.com/en/articles/15400594-claude-cowork-june-2026-usage-promotion
    It states that after August 19, 2026, 5-hour usage limits in Cowork return to their standard levels.
    Verifier: http-404Source ledger: not-foundai-release-receipts

    Next: Locate an official replacement, court copy, or archived version; keep the original URL and the recovery trail visible.

Access gap 60

The verifier could not obtain the document through its identified clients. That is a limit on Hugin, not a finding about the publisher or claim.

  1. openai.comCould not testInstrument conflict
    https://openai.com/index/introducing-openai-presence/
    The post is a July 22, 2026 OpenAI announcement about Presence.
    Verifier: http-403Source ledger: readai-release-receipts

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  2. congress.govCould not testInstrument conflict
    https://www.congress.gov/crs-product/IF12843
    Product IF12843 (In Focus) by Bart Elias; references P.L. 116-260 (Aircraft Certification, Safety, and Accountability Act of 2020) and P.L. 118-63 (FAA Reauthorization Act of 2024).
    Verifier: http-403Source ledger: readboeing-faa-safety-oversight

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  3. justice.govCould not test
    https://www.justice.gov/archives/opa/pr/boeing-charged-737-max-fraud-conspiracy-and-agrees-pay-over-25-billion
    Total criminal monetary amount over $2.5 billion: a $243.6 million criminal penalty, $1.77 billion in compensation to 737 MAX airline customers, and a $500 million crash-victim beneficiaries fund.
    Verifier: bot-challengeSource ledger: no-readable-textboeing-faa-safety-oversight

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  4. justice.govCould not test
    https://www.justice.gov/archives/opa/pr/boeing-charged-737-max-fraud-conspiracy-and-agrees-pay-over-25-billion
    Lion Air Flight 610 crashed October 29, 2018 and Ethiopian Airlines Flight 302 crashed March 10, 2019; together the crashes killed 346 people, and the 737 MAX was grounded in the United States on March 13, 2019.
    Verifier: bot-challengeSource ledger: no-readable-textboeing-faa-safety-oversight

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  5. govinfo.govCould not test
    https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20727.htm
    The order states: 'This order is effective October 9, 2026. The classification was applicable on November 15, 2023.'
    Verifier: timeoutSource ledger: readconsumer-protection-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  6. justice.govCould not test
    https://www.justice.gov/usao-edva/pr/eleven-defendants-sentenced-prison-hampton-roads-credit-union-parking-lot-scam
    It cites 'Case Nos. 2:25-cr-105 and 2:25-cr-128.'
    Verifier: bot-challengeSource ledger: no-readable-textconsumer-protection-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  7. justice.govCould not test
    https://www.justice.gov/usao-mdfl/pr/owner-semi-truck-business-indicted-operating-105-million-fraud-scheme
    It states the indictment notifies Lunsford 'that the United States is seeking an order of forfeiture in the amount of $105,940,214.93'.
    Verifier: bot-challengeSource ledger: no-readable-textconsumer-protection-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  8. justice.govCould not test
    https://www.justice.gov/usao-mdfl/pr/owner-semi-truck-business-indicted-operating-105-million-fraud-scheme
    It states: 'Between approximately December 2023 and May 2025, Lunsford and others solicited more than $105 million from victim-investors.'
    Verifier: bot-challengeSource ledger: no-readable-textconsumer-protection-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  9. justice.govCould not test
    https://www.justice.gov/usao-mdfl/pr/owner-semi-truck-business-indicted-operating-105-million-fraud-scheme
    It states Lunsford 'used approximately $75 million of new investors' funds to pay earlier investors and used over $25 million for his personal enrichment'.
    Verifier: bot-challengeSource ledger: no-readable-textconsumer-protection-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  10. justice.govCould not test
    https://www.justice.gov/usao-mdfl/pr/owner-semi-truck-business-indicted-operating-105-million-fraud-scheme
    It states: 'Lunsford used approximately $2 million of victim-investors' funds on business-related expenses and operations.'
    Verifier: bot-challengeSource ledger: no-readable-textconsumer-protection-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  11. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/bitfinex-hacker-sentenced-money-laundering-conspiracy-involving-billions-stolen
    Lichtenstein and his wife Heather Morgan each pleaded guilty on August 3, 2023 to one count of conspiracy to commit money laundering.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  12. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/founder-celsius-sentenced-12-years-fraud-and-market-manipulation
    Mashinsky, 59, was sentenced to 12 years plus three years of supervised release, a $50,000 fine, and forfeiture of $48,393,446, for commodities fraud and securities fraud.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  13. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/founder-celsius-sentenced-12-years-fraud-and-market-manipulation
    He pled guilty on December 3, 2024 before U.S. District Judge John G. Koeltl.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  14. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/founder-celsius-sentenced-12-years-fraud-and-market-manipulation
    Celsius held approximately $25 billion in assets at its peak; when it halted withdrawals on June 12, 2022, customers had $4.7 billion in inaccessible assets, and it filed for bankruptcy July 13, 2022.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  15. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/crypto-enabled-fraudster-sentenced-orchestrating-40-billion-fraud
    He was extradited on December 31, 2024 and pled guilty in August 2025 before U.S. District Judge Paul A. Engelmayer.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  16. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/crypto-enabled-fraudster-sentenced-orchestrating-40-billion-fraud
    He was ordered to forfeit over $19 million; the release states UST and LUNA crashed in May 2022, resulting in over $40 billion in investor losses.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  17. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/samuel-bankman-fried-sentenced-25-years-prison
    Bankman-Fried was sentenced to 25 years in prison, three years of supervised release, and over $11 billion in forfeiture, by U.S. District Judge Lewis A. Kaplan.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  18. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/samuel-bankman-fried-sentenced-25-years-prison
    The release states he defrauded FTX investors of more than $1.7 billion and Alameda lenders of more than $1.3 billion.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  19. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/investigations-cryptocurrency-scams-result-seizure-more-25-million
    It states that on July 21, 2026 the office "filed five civil forfeiture complaints in U.S. District Court seeking forfeiture of more than $25 million in cryptocurrency".
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  20. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/investigations-cryptocurrency-scams-result-seizure-more-25-million
    The five complaints seek approximately $10,400,913, $12,086,914, $1,230,900, $2,392,231 and $285,000.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  21. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/singaporean-ringleader-245-million-cryptocurrency-racketeering-enterprise-pleads-guilty
    It states Lam "pleaded guilty today in U.S. District Court in Washington D.C. in connection with his role as ringleader of an international cybercrime conspiracy that used social engineering to steal and launder cryptocurrency valued at more than $245 million".
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  22. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/singaporean-ringleader-245-million-cryptocurrency-racketeering-enterprise-pleads-guilty
    It states Lam pleaded guilty before Judge Colleen Kollar-Kotelly "to one count of participating in a RICO conspiracy" and that the judge "set a status hearing December 8, 2026."
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  23. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/scam-center-strike-force-conducts-seizures-chinese-run-illicit-scammer-marketplace-and
    It states: "On September 7, 2026, the U.S. District Court for the District of Columbia authorized seizure of the Telegram channels hosting this marketplace."
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  24. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/scam-center-strike-force-conducts-seizures-chinese-run-illicit-scammer-marketplace-and
    It states the Strike Force "seized two cryptocurrency wallets that Xinbi used to collect payments for vendors, which collectively held approximately $12 million in funds" and sought restraint of 47 additional wallets.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  25. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/scam-center-strike-force-conducts-seizures-chinese-run-illicit-scammer-marketplace-and
    It states approximately $52 million was restrained in one day, "bringing the total restrained by the Scam Center Strike Force to approximately $938 million."
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  26. justice.govCould not test
    https://www.justice.gov/usao-dc/pr/scam-center-strike-force-conducts-seizures-chinese-run-illicit-scammer-marketplace-and
    It cites IC3 figures that reported CIF losses rose "from $4.57 billion in 2023, to $8.65 billion in 2025, an increase of 89%."
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  27. justice.govCould not test
    https://www.justice.gov/usao-mdfl/pr/goliath-ventures-ceo-pleads-guilty-cryptocurrency-fraud-scheme-conspiracy
    It states: "In the plea agreement, Delgado has admitted to causing a minimum of $250 million in losses to investors."
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  28. justice.govCould not test
    https://www.justice.gov/usao-mdfl/pr/goliath-ventures-ceo-pleads-guilty-cryptocurrency-fraud-scheme-conspiracy
    It states: "As reflected in a companion civil asset forfeiture action, the United States has identified at least $400 million paid by investors to Goliath."
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  29. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/us-attorney-seeks-forfeiture-61-million-cryptocurrency-iranian-militarys-black-market
    It announces 'the filing of a civil forfeiture Complaint against approximately $61 million in cryptocurrency as the proceeds of black-market sales of sanctioned Iranian crude oil and petroleum products'.
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  30. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/us-attorney-seeks-forfeiture-61-million-cryptocurrency-iranian-militarys-black-market
    It states that addresses termed the 'Entity A' addresses 'have received and distributed more than approximately $1.5 billion of proceeds of the illicit sale of Iranian oil.'
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  31. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/two-robinhood-employees-charged-fraud
    It states: 'CHAI and XIANG each profited more than $50,000 from their illicit trading.'
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  32. justice.govCould not test
    https://www.justice.gov/usao-wdmo/pr/vietnamese-national-charged-role-massive-pig-butchering-cryptocurrency-scam
    It states: 'From Feb. 9, 2018, through Dec. 17, 2024, Van's cryptocurrency wallets received approximately $53,275,939 in cryptocurrency assets from wire fraud schemes targeting United States citizens.'
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  33. justice.govCould not test
    https://www.justice.gov/usao-wdmo/pr/vietnamese-national-charged-role-massive-pig-butchering-cryptocurrency-scam
    It states: 'The wallet transferred approximately $53,188,466 worth of the same cryptocurrency assets to other accounts off the centralized blockchain network.'
    Verifier: bot-challengeSource ledger: no-readable-textcrypto-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  34. congress.govCould not testInstrument conflict
    https://www.congress.gov/bill/119th-congress/house-bill/4405
    The bill became Public Law 119-38, requiring DOJ disclosure of Epstein-related records.
    Verifier: http-403Source ledger: readepstein-public-records

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  35. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/ghislaine-maxwell-charged-manhattan-federal-court-conspiring-jeffrey-epstein-sexually
    The release states Maxwell was arrested on July 2, 2020.
    Verifier: bot-challengeSource ledger: no-readable-textepstein-public-records

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  36. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/ghislaine-maxwell-sentenced-20-years-prison-conspiring-jeffrey-epstein-sexually-abuse
    Maxwell was sentenced to 240 months in prison on June 28, 2022.
    Verifier: bot-challengeSource ledger: no-readable-textepstein-public-records

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  37. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/ghislaine-maxwell-sentenced-20-years-prison-conspiring-jeffrey-epstein-sexually-abuse
    The release states Maxwell was previously found guilty on December 29, 2021.
    Verifier: bot-challengeSource ledger: no-readable-textepstein-public-records

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  38. justice.govCould not test
    https://www.justice.gov/usao-sdny/pr/statement-us-attorney-damian-williams-verdict-us-v-ghislaine-maxwell
    A jury found Maxwell guilty on December 29, 2021.
    Verifier: bot-challengeSource ledger: no-readable-textepstein-public-records

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  39. justice.govCould not test
    https://www.justice.gov/usao-ct/pr/connecticut-us-attorneys-office-announces-more-92-million-settlements-connected-ppp
    Beaver Paper & Graphic Media, Inc. and affiliates paid $2,933,219.96 over a $1,203,787 second-draw PPP loan; the government contends that together with its affiliates the company had more than 300 employees in March 2021.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  40. justice.govCould not test
    https://www.justice.gov/usao-ct/pr/connecticut-us-attorneys-office-announces-more-92-million-settlements-connected-ppp
    Fabbrica LLC agreed to pay $2,581,250 over a $2,000,000 second-draw PPP loan.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  41. justice.govCould not test
    https://www.justice.gov/usao-ct/pr/connecticut-us-attorneys-office-announces-more-92-million-settlements-connected-ppp
    United Abrasives, Inc. paid $3,088,605.45 over a second-draw PPP loan application for $1,983,555.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  42. justice.govCould not test
    https://www.justice.gov/usao-ct/pr/connecticut-us-attorneys-office-announces-more-92-million-settlements-connected-ppp
    Two further settlements, $400,000 on an ability-to-pay basis and $217,978, resolve allegations of false representations in connection with PPP loan forgiveness.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  43. justice.govCould not test
    https://www.justice.gov/usao-edpa/pr/dauphin-county-man-sentenced-10-years-prison-pandemic-unemployment-assistance-scheme
    The defendant was sentenced to 120 months in prison, three years of supervised release, and restitution of $3,177,376 by U.S. District Judge Juan R. Sánchez.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  44. justice.govCould not test
    https://www.justice.gov/usao-edpa/pr/dauphin-county-man-sentenced-10-years-prison-pandemic-unemployment-assistance-scheme
    The two co-defendants filed over 500 fraudulent PUA applications in 27 states using at least 375 identities of current or former employees of one company, resulting in a loss to the government of at least $2,886,876.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  45. justice.govCould not test
    https://www.justice.gov/usao-wdwa/pr/carnation-washington-man-sentenced-prison-covid-fraud-scheme-and-attempts-steal
    DOJ reports unemployment applications in 19 states and $148,206 paid by six states.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  46. justice.govCould not test
    https://www.justice.gov/usao-wdwa/pr/carnation-washington-man-sentenced-prison-covid-fraud-scheme-and-attempts-steal
    The $17,500 PPP application was approved but never paid, according to the release.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  47. justice.govCould not test
    https://www.justice.gov/usao-wdwa/pr/carnation-washington-man-sentenced-prison-covid-fraud-scheme-and-attempts-steal
    The defendant pleaded guilty July 2, 2026 and was sentenced October 5 to three years in prison and three years of supervised release.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  48. justice.govCould not test
    https://www.justice.gov/usao-wdwa/pr/carnation-washington-man-sentenced-prison-covid-fraud-scheme-and-attempts-steal
    The separately reported restitution total is $148,706.
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  49. justice.govCould not test
    https://www.justice.gov/usao-cdca/pr/inland-empire-man-pleads-guilty-his-role-crime-ring-fraudulently-obtained-35-million
    It states: 'Knighten admitted to causing at least $145,550 in losses to the PPP loan program.'
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  50. justice.govCould not test
    https://www.justice.gov/usao-cdca/pr/inland-empire-man-pleads-guilty-his-role-crime-ring-fraudulently-obtained-35-million
    It states: 'Federal prosecutors believe the total loss resulting from this scheme is approximately $3.5 million.'
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  51. justice.govCould not test
    https://www.justice.gov/usao-sdin/pr/former-veterans-affairs-field-examiner-indicted-federal-fraud-charge-related-covid-19
    It states: 'Bond allegedly applied for two EIDLs and two PPP loans, ultimately receiving approximately $101,333.'
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  52. justice.govCould not test
    https://www.justice.gov/usao-sdin/pr/former-veterans-affairs-field-examiner-indicted-federal-fraud-charge-related-covid-19
    It states: 'Bond made his initial appearance in federal court on September 16, 2026.'
    Verifier: bot-challengeSource ledger: no-readable-textpandemic-relief-fraud-enforcement

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  53. justice.govCould not test
    https://www.justice.gov/usao-edmi/pr/contractor-agrees-pay-one-largest-abilityone-program-related-false-claims-act
    The settlement amount is $5,059,808.00.
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  54. justice.govCould not test
    https://www.justice.gov/usao-edmi/pr/contractor-agrees-pay-one-largest-abilityone-program-related-false-claims-act
    The settlement resolves a qui tam lawsuit filed in the Eastern District of Michigan, Case No. 17-13804, against Global Connections to Employment, Inc.
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  55. justice.govCould not test
    https://www.justice.gov/usao-md/pr/taiwan-led-manufacturer-agrees-515m-settlement-false-claims-act-and-administrative
    The release is dated August 5, 2026 and states a settlement of $5.15 million.
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  56. justice.govCould not test
    https://www.justice.gov/usao-cdca/pr/veteran-sentenced-3-years-federal-prison-defrauding-navy-out-more-9-million-bid
    The defendant was sentenced to 36 months in federal prison and ordered to pay $9,128,515 in restitution.
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  57. justice.govCould not test
    https://www.justice.gov/usao-cdca/pr/veteran-sentenced-3-years-federal-prison-defrauding-navy-out-more-9-million-bid
    The co-conspirator, a Navy enlistee who held supervisory positions at MUSE, pleaded guilty on April 21 to one count of bribery of a public official and was sentenced on August 25 to 12 months and one day in federal prison and $97,960 in restitution.
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  58. justice.govCould not test
    https://www.justice.gov/usao-wdtx/pr/flores-family-agrees-pay-additional-25-million-civil-penalties-defrauding-united
    It states the agreements 'require the defendants to collectively pay $2.5 million in civil penalties under the False Claims Act.'
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  59. justice.govCould not test
    https://www.justice.gov/usao-wdtx/pr/flores-family-agrees-pay-additional-25-million-civil-penalties-defrauding-united
    It states 'KDHK, Inc., Kenneth Flores, and Irma Flores will jointly pay the United States $2,000,000, and Christopher Flores will individually pay the United States $500,000'.
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

  60. justice.govCould not test
    https://www.justice.gov/usao-wdtx/pr/flores-family-agrees-pay-additional-25-million-civil-penalties-defrauding-united
    It states the United States 'previously obtained judgments imposing a total of $547,613.92 in civil penalties against the two federal employees who conspired with the Flores family.'
    Verifier: bot-challengeSource ledger: no-readable-textpublic-spending-misuse-review

    Next: Repeat with an identified independent client or a manual read. Never convert a refusal into an absent finding.

Document identity gap 41

The fetched body could not be proven to be the cited document, or the fingerprint was too weak to distinguish it from page furniture.

  1. cnbc.comCould not test
    https://www.cnbc.com/2026/07/08/openai-expanding-gpt-5point6-ai-model-release-ending-government-limits.html
    The report keeps the public launch on Thursday, July 9, 2026 for all three GPT-5.6 models.
    Looked for: July 9, 2026Verifier: identity-unconfirmed:1/3-termsSource ledger: readai-release-receipts

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  2. ai.google.devCould not test
    https://ai.google.dev/gemini-api/docs/deprecations
    gemini-omni-flash-preview is listed with shutdown date September 30, 2026 and replacement gemini-omni-1.1-flash.
    Looked for: September 30, 2026Verifier: too-few-distinctive-termsSource ledger: readai-release-receipts

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  3. govinfo.govCould not test
    https://www.govinfo.gov/content/pkg/FR-2020-11-20/pdf/2020-25844.pdf
    It was filed 11-18-20 and published at 85 FR 74560 on November 20, 2020, document number 2020-25844.
    Looked for: 85 FR 74560Verifier: too-few-distinctive-termsSource ledger: readboeing-faa-safety-oversight

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  4. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/06/24/2026-12749/safety-standard-for-lithium-ion-batteries-used-in-micromobility-products-and-electrical-systems-of
    Its DATES section set written comments due August 24, 2026, and required any person interested in making an oral presentation to email the Office of the Secretary by July 24, 2026.
    Looked for: August 24, 2026, July 24, 2026Verifier: identity-unconfirmed:0/10-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  5. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/24/2026-19579/substantial-product-hazard-list-amendments-to-requirements-for-window-covering-cords
    Written comments must be received by November 23, 2026.
    Looked for: November 23, 2026Verifier: identity-unconfirmed:0/9-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  6. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/24/2026-19579/substantial-product-hazard-list-amendments-to-requirements-for-window-covering-cords
    On September 22, 2026, the Commission voted 3-0 to publish the notice of proposed rulemaking.
    Looked for: September 22, 2026Verifier: identity-unconfirmed:0/9-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  7. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/22/2026-19289/fleetcor-technologies-analysis-of-proposed-consent-order-to-aid-public-comment
    FR Doc 2026-19289, printed at 91 FR 60133-60134, published September 22, 2026.
    Looked for: 91 FR 60133, September 22, 2026Verifier: identity-unconfirmed:0/6-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  8. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/22/2026-19289/fleetcor-technologies-analysis-of-proposed-consent-order-to-aid-public-comment
    Comments must be received on or before October 22, 2026.
    Looked for: October 22, 2026Verifier: identity-unconfirmed:0/6-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  9. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/22/2026-19289/fleetcor-technologies-analysis-of-proposed-consent-order-to-aid-public-comment
    The Eleventh Circuit affirmed that Corpay, Inc. is liable on all five counts and affirmed the permanent injunction against it, and determined the CEO is liable on Counts I, III, IV, and V but not Count II, in FTC v. Corpay, Inc., 164 F.4th 807 (11th Cir. 2026).
    Looked for: 164 F.4th 807Verifier: identity-unconfirmed:0/6-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  10. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/22/2026-19289/fleetcor-technologies-analysis-of-proposed-consent-order-to-aid-public-comment
    Provision I requires Respondents to pay the Commission $100,000,000 in monetary relief, and the order would terminate in 20 years if Respondents meet all obligations.
    Looked for: $100,000,000Verifier: identity-unconfirmed:0/6-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  11. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/23/2026-19493/patient-protection-and-affordable-care-act-temporary-moratoria-on-certain-agent-and-broker
    FR Doc 2026-19493, printed at 91 FR 60317-60334, published September 23, 2026; effective September 22, 2026; comments must be received by November 21, 2026 (regulations.gov docket CMS-2026-3202, file code CMS-9872-IFC).
    Looked for: 91 FR 60317, September 23, 2026, September 22, 2026, November 21, 2026Verifier: identity-unconfirmed:0/9-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  12. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/23/2026-19493/patient-protection-and-affordable-care-act-temporary-moratoria-on-certain-agent-and-broker
    The moratorium remains in effect until February 1, 2027 unless CMS lifts it earlier, extends it, or otherwise modifies it by Federal Register notice.
    Looked for: February 1, 2027Verifier: identity-unconfirmed:0/9-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  13. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/23/2026-19493/patient-protection-and-affordable-care-act-temporary-moratoria-on-certain-agent-and-broker
    On August 31, 2026, CMS cancelled approximately 315,000 Plan Year 2026 policies covering over 760,000 individuals that were enrolled with agent or broker assistance without verified citizenship or immigration documentation and for whom issuers could not identify claims or establish consumer contact.
    Looked for: August 31, 2026Verifier: identity-unconfirmed:0/9-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  14. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/10/08/2026-20648/notice-of-intent-to-establish-a-negotiated-rulemaking-advisory-committee-for-vehicle-lighting
    Its DATES line states: 'Comments on the intent to establish the committee and the proposed membership must be received by November 9, 2026. Applications for membership must be received by NHTSA on or before 5 p.m. ET November 9, 2026.'
    Looked for: November 9, 2026, November 9, 2026Verifier: identity-unconfirmed:0/9-termsSource ledger: redirectedconsumer-protection-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  15. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/25/2026-19643/privacy-act-of-1974-matching-program
    FR Doc 2026-19643, printed at 91 FR 60958-60959, published September 25, 2026; comments due October 26, 2026.
    Looked for: 91 FR 60958, September 25, 2026, October 26, 2026Verifier: identity-unconfirmed:1/8-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  16. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/25/2026-19643/privacy-act-of-1974-matching-program
    The matching program will run for an initial term of 36 months, approximately October 19, 2026 to October 18, 2029, renewable for three years.
    Looked for: October 19, 2026, October 18, 2029Verifier: identity-unconfirmed:1/8-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  17. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/25/2026-19643/privacy-act-of-1974-matching-program
    It re-establishes matching begun in 2020 to address improper payments using the Do Not Pay Working System (85 FR 58062).
    Looked for: 85 FR 58062Verifier: identity-unconfirmed:1/8-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  18. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/02/2026-17963/privacy-act-of-1974-matching-program
    Published September 2, 2026 at 91 FR 56474, FR Doc 2026-17963.
    Looked for: 91 FR 56474, September 2, 2026Verifier: identity-unconfirmed:1/5-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  19. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/01/2026-17838/privacy-act-of-1974-system-of-records
    Published September 1, 2026 at 91 FR 56223, FR Doc 2026-17838.
    Looked for: 91 FR 56223, September 1, 2026Verifier: identity-unconfirmed:1/5-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  20. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/02/2026-17907/privacy-act-of-1974-matching-program
    Published September 2, 2026 at 91 FR 56457, FR Doc 2026-17907.
    Looked for: 91 FR 56457, September 2, 2026Verifier: identity-unconfirmed:1/5-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  21. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/11/2026-18527/privacy-act-of-1974-matching-program
    FR Doc 2026-18527, printed at pages 57950-57952, published September 11, 2026.
    Looked for: September 11, 2026Verifier: identity-unconfirmed:1/5-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  22. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/11/2026-18527/privacy-act-of-1974-matching-program
    The notice states the modified matching program will be effective 30 days after publication through September 10, 2029.
    Looked for: September 10, 2029Verifier: identity-unconfirmed:1/5-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  23. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/11/2026-18527/privacy-act-of-1974-matching-program
    It rescinds and replaces the SBA notice published on October 10, 2023 (88 FR 69978), and cites OMB Memorandum M-25-32.
    Looked for: 88 FR 69978, October 10, 2023Verifier: identity-unconfirmed:1/5-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  24. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/24/2026-19599/privacy-act-of-1974-matching-program
    FR Doc 2026-19599, printed at 91 FR 60677, published September 24, 2026.
    Looked for: 91 FR 60677, September 24, 2026Verifier: identity-unconfirmed:1/4-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  25. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/24/2026-19599/privacy-act-of-1974-matching-program
    The correction states the September 11, 2026 document inadvertently omitted the associated Privacy Act System of Records in the Appendix.
    Looked for: September 11, 2026Verifier: identity-unconfirmed:1/4-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  26. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/24/2026-19599/privacy-act-of-1974-matching-program
    The corrected Appendix states the OMB M-25-32 routine use has been added to SBA 20 — Disaster Loans Case Files (91 FR 56700) and SBA 21 — Loan System (91 FR 56703), published September 3, 2026.
    Looked for: 91 FR 56700, 91 FR 56703, September 3, 2026Verifier: identity-unconfirmed:1/4-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  27. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/15/2026-18801/privacy-act-of-1974-system-of-records
    FR Doc 2026-18801, printed at 91 FR 58520-58521, published September 15, 2026; comments due October 15, 2026.
    Looked for: 91 FR 58520, September 15, 2026, October 15, 2026Verifier: identity-unconfirmed:2/8-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  28. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/15/2026-18801/privacy-act-of-1974-system-of-records
    The program will become effective 30 days after publication, absent comments requiring changes, and remain in effect through September 10, 2029.
    Looked for: September 10, 2029Verifier: identity-unconfirmed:2/8-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  29. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/08/18/2026-16800/designation-of-databases-to-the-do-not-pay-working-system
    FR Doc 2026-16800, printed at page 53483, published August 18, 2026, under docket TREAS-DO-2026-0430.
    Looked for: August 18, 2026Verifier: identity-unconfirmed:0/8-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  30. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/08/18/2026-16800/designation-of-databases-to-the-do-not-pay-working-system
    Treasury published a notice on June 25, 2026 proposing the designation and received no comments during the 15-day comment period.
    Looked for: June 25, 2026Verifier: identity-unconfirmed:0/8-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  31. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/03/2026-18034/privacy-act-of-1974-matching-program
    Published September 3, 2026 at 91 FR 56613, FR Doc 2026-18034.
    Looked for: 91 FR 56613, September 3, 2026Verifier: identity-unconfirmed:1/4-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  32. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/03/2026-18034/privacy-act-of-1974-matching-program
    It states the program will remain in effect through September 10, 2029, and that Treasury, in consultation with OMB, has issued a waiver of the matching agreement requirement.
    Looked for: September 10, 2029Verifier: identity-unconfirmed:1/4-termsSource ledger: redirectedgao-federal-improper-payments-fy2025

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  33. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/11/2026-18527/privacy-act-of-1974-matching-program
    FR Doc 2026-18527, printed at pages 57950-57952, published September 11, 2026.
    Looked for: September 11, 2026Verifier: identity-unconfirmed:1/6-termsSource ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  34. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/11/2026-18527/privacy-act-of-1974-matching-program
    The notice states the modified matching program will be effective 30 days after publication through September 10, 2029.
    Looked for: September 10, 2029Verifier: identity-unconfirmed:1/6-termsSource ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  35. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/09/11/2026-18527/privacy-act-of-1974-matching-program
    It rescinds and replaces the SBA notice published on October 10, 2023 (88 FR 69978), and cites OMB Memorandum M-25-32.
    Looked for: 88 FR 69978, October 10, 2023Verifier: identity-unconfirmed:1/6-termsSource ledger: redirectedpandemic-relief-fraud-enforcement

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  36. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/08/18/2026-16800/designation-of-databases-to-the-do-not-pay-working-system
    FR Doc 2026-16800, printed at page 53483, published August 18, 2026, under docket TREAS-DO-2026-0430.
    Looked for: August 18, 2026Verifier: identity-unconfirmed:0/8-termsSource ledger: redirectedpublic-spending-misuse-review

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  37. federalregister.govCould not test
    https://www.federalregister.gov/documents/2026/08/18/2026-16800/designation-of-databases-to-the-do-not-pay-working-system
    Treasury published a notice on June 25, 2026 proposing the designation and received no comments during the 15-day comment period.
    Looked for: June 25, 2026Verifier: identity-unconfirmed:0/8-termsSource ledger: redirectedpublic-spending-misuse-review

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  38. storage.courtlistener.comCould not test
    https://storage.courtlistener.com/recap/gov.uscourts.vaed.607104/gov.uscourts.vaed.607104.37.0.pdf
    The execution paragraph charges that 'on or about January 23, 2026, the defendant caused Individual 2, from an office location in the Eastern District of Virginia, to initiate a wire transfer of approximately $45,000,000 from Company 1 to Holding Company 1's bank account, via a server located outside of the Commonwealth of Virginia, by falsely representing the material facts that there existed a SAP #1'.
    Looked for: $45,000,000, January 23, 2026Verifier: identity-unconfirmed:1/5-termsSource ledger: readpublic-spending-misuse-review

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  39. storage.courtlistener.comCould not test
    https://storage.courtlistener.com/recap/gov.uscourts.vaed.607104/gov.uscourts.vaed.607104.37.0.pdf
    Paragraph 41 reads: 'Between in and around November 2025 and in and around March 2026, RUSH caused Company 1 to transfer approximately $145 million to Holding Company 1 in multiple financial transactions.'
    Looked for: $145 millionVerifier: identity-unconfirmed:1/5-termsSource ledger: readpublic-spending-misuse-review

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  40. storage.courtlistener.comCould not test
    https://storage.courtlistener.com/recap/gov.uscourts.vaed.607104/gov.uscourts.vaed.607104.37.0.pdf
    The forfeiture allegation lists 'a monetary judgment in the amount of at least $193,590,400.69 representing the amount of proceeds the defendant obtained as a result of the violations described in this Information', $38,651,314.55 seized from a Bank of America account held in the name of 0701 Holdings LLC, four Florida properties, two 2026 BMW Alpina XB7s, 298 gold bars, $2,106,550 in U.S. currency, €104,795, '30 watches seized from the defendant's residence', 'four watches seized from a residence in Warrenton, Virginia' and 'one Rolex Oyster Perpetual Sea-Dweller 4000 (Model 11660)' listed on its own line; this desk does not total the watch entries, because the document does not say whether the named Rolex is one of the others.
    Looked for: $193,590,400.69, $38,651,314.55, $2,106,550Verifier: identity-unconfirmed:1/5-termsSource ledger: readpublic-spending-misuse-review

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

  41. storage.courtlistener.comCould not test
    https://storage.courtlistener.com/recap/gov.uscourts.vaed.607104/gov.uscourts.vaed.607104.37.0.pdf
    Paragraph 14 states RUSH 'served in the United States Navy and was honorably discharged from the reserves effective February 1, 2015', against representations that he was a military pilot with a bachelor's and a doctoral degree, which paragraph 13 states were false.
    Looked for: February 1, 2015Verifier: identity-unconfirmed:1/5-termsSource ledger: readpublic-spending-misuse-review

    Next: Strengthen the anchor label or fingerprint with distinctive terms, then confirm the fetched body before scoring any absence.

Instrument gap 1

The fact carries a checkable value, but the verifier does not yet have a safer, more specific explanation for why it could not score it.

  1. oversight.govCould not test
    https://www.oversight.gov/boeing-charged-737-max-fraud-conspiracy-agrees-pay-25-billion
    Records the January 7, 2021 resolution with its three monetary components (a $243.6 million penalty, $1.77 billion in customer compensation, and a $500 million victim beneficiaries fund).
    Verifier: http-406Source ledger: unreachableboeing-faa-safety-oversight

    Next: Inspect the stored reason and add a deterministic check before treating the claim as confirmed or absent.

The verification calendar

A dated term can be put on a calendar before anything happens. When a published entry commits this desk to checking something on a date, the commitment is listed here — and the outcome only appears once a published entry records it. The calendar never resolves itself; it points at the record that did.

A past-due row with nothing filed stays on this page under exactly that label, because a desk that quietly drops its own scheduled checks is doing the thing it criticises.

  1. The date moved
    Did Anthropic's doubled Cowork usage limits lapse on August 5 as stated, extend, or pass without a provider record?
    Filed August 6, 2026: The window moved. The launch post still reads August 5, unchanged — the extension through August 19 was published by editing the help-center article the post links to, whose own timestamp is relative. Read the entry that records it
  2. Could not be established — a limit on this desk
    Did the Atlas browser stop working on August 9 as OpenAI's release notes scheduled it — and can this desk establish that from an OpenAI page at all?
    Filed August 10, 2026: Not establishable by this desk's own instrument. Every OpenAI page governing the consumer-facing retirement either refuses the identifying client outright or answers it with a bot challenge, while the developer docs answer the same client with the full document. The retirement is reported by third parties; Hugin records the refusal instead of borrowing a browser identity to claim a read. Read the entry that records it
    Last instrument reading of the operative pages: 2 recorded terms present · 2 terms the page repeats 6+ times — presence here may not be about this record
  3. Kept as stated
    Did gpt-5.2-chat-latest and gpt-5.3-chat-latest actually leave the API on August 10, as the deprecations ledger scheduled on May 8?
    Filed August 10, 2026: Executed on schedule. Read today with the identifying client: the deprecations ledger still carries both ids against "Aug 10, 2026" with gpt-5.6-sol as the replacement, and neither id appears anywhere on the live models list — no "-chat-latest" alias does. Read the entry that records it
    Last instrument reading of the operative pages: 5 recorded terms present · 2 terms confirmed gone as scheduled · 1 term the page repeats 6+ times — presence here may not be about this record
  4. Could not be established — a limit on this desk
    Did the extended Cowork window end on August 19 as the help-center article states, extend again, or pass without a record?
    Filed August 20, 2026: Not establishable. The operative terms article returned HTTP 404 on five attempts across two clients, and a site-scoped search of the support centre surfaced no replacement usage-promotion article. Both watched expectations are therefore recorded as unscored rather than absent — a page that will not load contains nothing, and scoring it would manufacture a finding. The announcement post remains live, carries no update note, and still advertises "through August 5", a date superseded twice. The likeliest explanation is ordinary housekeeping of an expired promotion; the effect is that no reachable page states Cowork's current terms. Read the entry that records it
    Last instrument reading of the operative pages: 1 recorded term present · 1 page declined the automated read after repeated attempts
  5. The date moved
    Did the +50% Claude Code weekly-limit window end on August 19, renew again, or lapse quietly past its stated date — which it has done once already?
    Filed August 20, 2026: Extended again, silently. The watched string "August 19, 2026" is gone from the operative article at zero occurrences — but not because the window closed: the page now reads "From May 13, 2026 through August 31, 2026" under the same "We've extended this promotion" note it has carried through every prior extension, and states that weekly limits return to standard levels after August 31. No announcement post and no changelog entry accompanied it, so the new date exists only inside the article. That is precisely why this row was re-anchored to the operative page on August 7 instead of the social post it originally watched. Read the entry that records it
    Last instrument reading of the operative pages: 1 no longer found
  6. Partly established
    Did OpenAI's two August 26 retirements — o3 from ChatGPT and the Assistants API shutdown — happen as their pages schedule them?
    Filed August 27, 2026: The Assistants API shutdown was confirmed by controlled wire probes against a known-missing route; o3's ChatGPT retirement was not establishable from the public pages this desk could read, and was left unresolved rather than inferred from a schedule page. Read the entry that records it
    Last instrument reading of the operative pages: 3 recorded terms present
  7. Could not be established — a limit on this desk
    Did the official DALL·E GPT retire from ChatGPT on August 30 — and can this desk establish that from an OpenAI page at all, given that the notice lives on a host that refuses it?
    Filed September 1, 2026: Not establishable. The only operative page declined this desk's identifying client on three spaced attempts on the due day, as it has on every sweep since August 7. Filed as a limit of this desk rather than left reading as a check nobody ran; nothing here says whether DALL·E retired on schedule. Read the entry that records it
    Last instrument reading of the operative pages: 2 recorded terms present
  8. Missed — the date passed
    Did GPT-5.4 and GPT-5.4 mini actually stop being offered in Codex for ChatGPT sign-ins on August 31, as the Codex models doc schedules?
    Filed September 1, 2026: Lingered. Read at 19:42Z, twelve hours and forty-two minutes after August 31 ended in California: the page still says the models 'retire from Codex with ChatGPT sign-in on August 31, 2026' and still hands every reader the 'codex -m gpt-5.4' copy command, twice. The first LINGERING this instrument has produced, and on the provider's clock rather than UTC. Its limit is on the same page: API-key access 'isn't affected', and a page reader cannot tell which reader the offer is for — so what is established is that the offer outlived the date beside it, not that the model refuses a ChatGPT sign-in. Read the entry that records it
    Last instrument reading of the operative pages: 1 recorded term present · 1 still listed after the date it was due to go
  9. Reversed by the provider
    Does Anthropic's pricing page carry the standard $3/$15 per million token language it promised for September 1?
    Filed September 1, 2026: Reversed — and the check passed anyway. The page now reads: the $2/$10 pricing 'announced at launch as introductory pricing through August 31, 2026, is now the standard price. The previously scheduled increase to $3/$15 per million input/output tokens on September 1, 2026 will not occur.' Both watched strings survived inside the sentence that cancels the thing they were watching for. The instrument reported this window kept on schedule; it was not. Read the entry that records it
    Last instrument reading of the operative pages: 2 recorded terms present
  10. The date moved
    The Claude Code weekly-limit boost was extended to August 31, 2026 without an announcement. Does THIS window end on its stated date, extend a third time, or move again in silence?
    Filed September 1, 2026: Extended a third time. The article, marked 'Updated today', now reads 'Increased weekly limits now run through September 13, 2026' — and its terms state, for the first time on any page this desk watches, a timezone: 'valid from May 13, 2026 through September 13, 2026 at 11:59 PM PT'. The title still says May–August. The successor row is claude-code-weekly-boost-2026-09-14. Read the entry that records it
    Last instrument reading of the operative pages: 1 recorded term present · 1 no longer found
  11. Partly established
    Two weeks after the Cowork usage-promotion terms article started returning 404: has it come back at its old URL, appeared at a new one, or stayed gone — and does ANY reachable page yet state what Cowork's 5-hour limits currently are?
    Filed September 14, 2026: Stayed gone. The article answered HTTP 404 again at 2026-09-14T07:54Z; a search of the support centre surfaced no replacement terms article; and the launch post still reads 'through August 5'. The nearest page, 'Get started with Claude Cowork' (updated 2026-09-02), says Cowork tasks consume 'more of your usage allocation than chatting with Claude' and states no limit. The article's absence is measured; that no page anywhere states the current limits is a search result, and a search cannot prove a negative. Read the entry that records it
    Last instrument reading of the operative pages: 1 recorded term present · 1 page declined the automated read after repeated attempts
  12. Kept as stated
    The Claude Code weekly-limit boost was extended a third time, to September 13, 2026 at 11:59 PM PT — the first stated timezone on any page this desk watches. Does THIS window end on its stated date, extend a fourth time, or move again in silence?
    Filed September 14, 2026: Ended as stated, on the provider's own clock: the article was rewritten at 2026-09-14T06:59:42Z (11:59:42 PM PT) and now reads 'It ran from May 13 through September 13, 2026' and 'This offer was valid from May 13, 2026 through September 13, 2026 at 11:59 PM PT.' The promise to 'return to their standard levels' is gone — replaced by 'starting September 14, 2026, weekly limits in Claude Code are 25% higher than they were before the promotion for Pro, Max, Team, and seat-based Enterprise plans.' The window ended; the limits did not fall back. The title still says May–August. Read the entry that records it
    Last instrument reading of the operative pages: 2 recorded terms present · 1 no longer found
  13. Kept as stated
    The Videos API and the sora-2 model family are scheduled to shut down on September 24, 2026 — the only six pending rows on OpenAI's ledger whose replacement column is empty. Does the ledger still carry that schedule the day after, and does the help centre's stated API date still agree with it?
    Filed September 27, 2026: Executed by OpenAI's own account, and neither page this row watches records it. The sora-2 model page reads: 'The Sora 2 models and Videos API were shut down on September 24, 2026 and are no longer available. There is no one-to-one replacement API.' Unauthenticated, GET and POST /v1/videos answer 404 with an empty body — the same answer as a made-up route and the retired /v1/assistants — while /v1/models answers 401 with a JSON error (2026-09-28T03:57Z). Both questions this row asked hold: the ledger still carries all six rows dated 2026-09-24 with '—' in the replacement column, still under 'Upcoming deprecations', and the help-centre article, updated August 31, still says 'The Sora API will be discontinued on September 24, 2026' — the two dates agree, and both pages still speak of the shutdown as ahead three days after it. The hour of the shutdown is OpenAI's statement; this desk has no reading of /v1/videos from before the date and holds no key. Read the entry that records it
    Last instrument reading of the operative pages: 4 recorded terms present
  14. Kept as stated
    Four legacy completion models — gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 — are scheduled to shut down on September 28, 2026, under a notice published on September 26, 2025. Does the ledger still carry that schedule a year and two days after it was announced?
    Filed October 2, 2026: The ledger kept the schedule to the day: all four ids still sit against 2026-09-28 with gpt-5.6-terra named for each, and the section now sits under 'Past deprecations' (it was under 'Upcoming deprecations' on the morning of September 28, and under 'Past' by the evening of September 30). Its paragraph still says access 'will be shut down', while a same-day sibling section was rewritten to 'was shut down'. The page establishes the schedule, not the shutdown; no request was made to the models. Read the entry that records it
    Last instrument reading of the operative pages: 3 recorded terms present · 3 terms the page repeats 6+ times — presence here may not be about this record
  15. Past due — nothing filed
    Google's Gemini API changelog states the gemini-omni-flash-preview endpoint will be deprecated on September 30, 2026, with gemini-omni-1.1-flash released as the GA version. Does the changelog still carry that date the day after, and does it record what happened?
    Instrument: Re-read the Gemini API changelog's 2026-08-27 entry and quote its deprecation sentence. ⚠ The changelog redirects a plain unauthenticated client to a sign-in page; if the instrument reports it unread, that is a limit of this desk's reach and must be filed as not establishable, never as a pass. ⚠ Since September 30 the deprecations table no longer lists gemini-omni-flash-preview at all: the row was deleted, not grayed, though the page says 'Already-shutdown models are indicated with gray backgrounds'. A deleted row is not Google's record that the endpoint shut down; quote the changelog and the table as they read, and file the deletion as a reading of the page.
    Last instrument reading of the operative pages: 4 recorded terms present
  16. Past due — nothing filed
    Mistral's changelog entry of June 30, 2026 says the free Labs model Leanstral 1.5 (labs-leanstral-1-5) 'will be retired on September 30, 2026', while Mistral's models page still lists it among 'Other specialist models' rather than in its deprecated and retired table, its model page states no retirement date, and Mistral's lifecycle policy says 'Deprecation is announced as soon as a replacement model is available' with no replacement named. On October 1, which page does Mistral follow: does the changelog still carry the date, has the models page moved Leanstral 1.5 into the retired table, and does any page name a successor?
    Instrument: Re-read the changelog's June 30 entry and quote its retirement sentence; re-read the models page and record whether Leanstral 1.5 is still listed under 'Other specialist models' or has a row in the 'Deprecated & retired models' table, and what that row names as the alternative. ⚠ The listing term failing is the expected sign of a retirement, not a fault in the instrument. ⚠ This desk cannot call the endpoint (unauthenticated calls answer 401 whatever the model), so a retirement on the pages is a reading of the pages, never an observation that requests fail with the 404 Mistral's policy describes.
    Last instrument reading of the operative pages: 5 recorded terms present
  17. Past due — nothing filed
    Amazon's Bedrock legacy lifecycle table lists Nova Canvas (amazon.nova-canvas-v1:0) and Nova Reel (amazon.nova-reel-v1:0 and amazon.nova-reel-v1:1) with an end-of-life date of September 30, 2026 and no public extended access date, and says that on or soon after an end-of-life date requests to the model 'will fail' unless privately arranged; neither the table nor either model card names a replacement. Does the table still list September 30 the day after, do the model cards mark the models end of life, and does any page name a successor?
    Instrument: Re-read the legacy table's three Nova rows and both model cards, and quote the dates and lifecycle labels. ⚠ Amazon says requests fail 'on, or soon after' the date, so a model still listed the day after is not a missed date. ⚠ The table says it leaves out models already past end of life, yet on September 28 it still listed Nova Premier and Nova Sonic, whose date was September 14: a Nova row still there after September 30 is a reading of the page, and a row gone is not proof either. ⚠ This desk holds no AWS account and calls no model.
    Last instrument reading of the operative pages: 8 recorded terms present
  18. Past due — nothing filed
    OpenAI's ledger, in a section dated 2026-09-11, states gpt-5.4-cyber will be removed from the API on October 1, 2026, with gpt-5.6-cyber as the replacement — twenty days' notice. Does the ledger still carry that schedule the day after?
    Instrument: Re-read the ledger's 2026-09-11 section and quote its dated row. Twenty days is the shortest notice on the ledger's pending schedule; whether the date holds is the reading. ⚠ Since September 30 the section names no replacement model: it reads 'Migrate to the most capable cyber model available to you' where it named gpt-5.6-cyber. The commitment above keeps the replacement it was published with; the day after, quote what the replacement column says then.
    Last instrument reading of the operative pages: 3 recorded terms present
  19. Past due — nothing filed
    OpenAI's custom GPT retirement and migration FAQ lists 'Oct 1, 2026: Target for the migration banner in workspaces that already opted into delayed migration banners', and elsewhere says those workspaces 'have an Oct 1, 2026 banner target'. This is a TARGET, not a promise: the FAQ calls it a target, says of the neighbouring September 22 target that 'This is a target, not a guarantee that the option is available in every workspace', and says the Enterprise dates are subject to change. A banner that has not appeared on October 1 is therefore not a broken promise and must not be filed as one. Does the FAQ still name October 1 as the target the day after, has the target moved, or has the line been dropped?
    Instrument: Re-read the FAQ's Enterprise milestone list and its migration answer, and quote both October 1 lines. ⚠ This row measures what the page says about a target date, never whether a banner appeared: this desk holds no Enterprise workspace and cannot see in-product banners. A target the page still names after its day is a reading to report, not a miss; a moved or dropped line is filed as moved or reversed with the quote. ⚠ The FAQ was rewritten between September 16 and September 25 without a release note, which is when this milestone first appeared. ⚠ help.openai.com refuses node fetch and answers curl on the same identifying user-agent only some of the time; an unread page is a limit of this desk, never a pass.
    Last instrument reading of the operative pages: 2 recorded terms present
  20. Past due — nothing filed
    Microsoft's Foundry retirement schedule, last updated September 21, 2026, lists its own Preview image models MAI-Image-2.5-Pro, MAI-Image-2.5-Flash and MAI-Image-2.5 for retirement on October 1, 2026, each with '—' in the Replacement column, although the same table lists MAI-Image-2.5 and MAI-Image-2.5-Flash as the replacements for MAI-Image-2 and MAI-Image-2e, retired August 15. Microsoft says Preview dates are 'not sooner than' dates it sometimes extends. The day after, does the schedule still list October 1, was it extended, does it name a replacement, and does it mark the three retired?
    Instrument: Re-read the schedule's Microsoft table and quote the five MAI-Image rows; check Microsoft's MAI image how-to page (https://learn.microsoft.com/en-us/azure/foundry/foundry-models/how-to/use-foundry-models-mai-image), which on September 28 listed MAI-Image-2.6 and MAI-Image-2.6-Flash without calling them replacements, for any change. ⚠ Preview dates are floors Microsoft says it sometimes extends: a later date is 'moved', never 'missed'. ⚠ This desk cannot test Foundry deployments; a row marked Retired is a reading of the page, not proof that inference returns 410 Gone.
    Last instrument reading of the operative pages: 4 recorded terms present
  21. The date moved
    Google's Gemini API deprecations page, last updated September 5, 2026, lists gemini-2.5-flash-image with a shutdown date of October 2, 2026 and gemini-3.1-flash-image-preview as the replacement — under a caveat that listed dates are 'the earliest possible dates on which a model might be retired'. Does the row still read the same the day after, and does the page ever say whether the model was retired?
    Filed October 7, 2026: The date moved, and it was announced on a different surface. Read again on October 7, the deprecations table gives gemini-2.5-flash-image a shutdown of March 15, 2027 and names gemini-3.1-flash-lite-image, where the same page on September 27 read October 2, 2026 and gemini-3.1-flash-image-preview. An Agent Platform release note of September 14 had already recorded that model as 'extended from October 2, 2026' for Google Cloud, so the two surfaces now agree — but the pricing page watched by this row still carried the October 2 warning verbatim on the evening the old date fell due. Read the entry that records it
    Last instrument reading of the operative pages: 3 recorded terms present
  22. Past due — nothing filed
    GitHub states it will deprecate Gemini 3.5 Flash, Gemini 3.6 Flash, Kimi K2.7 Code and Claude Opus 4.7 across all Copilot experiences on October 2, 2026 — while Anthropic lists Opus 4.7 as Active, not sooner than April 16, 2027. Does the notice still carry that date and those four models the day after, and does GitHub record the change as done?
    Instrument: Re-read GitHub's 2026-09-03 changelog post and quote its table; check the changelog index for a follow-up retirement post. ⚠ The model's maker is NOT the operative page for this row — Anthropic's Active status is context, not evidence either way.
    Last instrument reading of the operative pages: 3 recorded terms present
  23. Past due — nothing filed
    Microsoft's Foundry retirement schedule lists Moonshot AI's Kimi-K2.7-Code, a Preview model sold by Azure, for retirement on October 3, 2026 with '—' in the Replacement column, the day after GitHub Copilot drops the same model and suggests Kimi K3 instead. Does the schedule still list October 3 the day after, was it extended, does it name a replacement, and does it mark the model retired?
    Instrument: Re-read the schedule's MoonshotAI table and quote the Kimi-K2.7-Code row. ⚠ A Preview date is a floor Microsoft says it sometimes extends: a later date is 'moved', never 'missed'. ⚠ The Copilot removal on October 2 is GitHub's and has its own row; this row measures Microsoft's page only, and this desk cannot test Foundry deployments.
    Last instrument reading of the operative pages: 1 no longer found
  24. Past due — nothing filed
    Google's Gemini API pages list the managed agent antigravity-preview-05-2026 with an October 5, 2026 shutdown date and antigravity-preview-09-2026 as its replacement. The deprecations table qualifies listed dates as the earliest possible shutdown dates. On October 6, do the pages still carry that schedule, and do they say the endpoint was actually retired?
    Instrument: Re-read the Gemini API changelog, deprecations table and Antigravity model page. Record the current date, replacement and earliest-possible caveat. These pages report Google's schedule; without an endpoint test, they do not establish whether the service is available.
    Last instrument reading of the operative pages: 9 recorded terms present
  25. Past due — nothing filed
    OpenAI's API pricing page states 'Billing for gpt-rosalind-research begins on October 5, 2026.' and lists the model at $5.00 per 1M input tokens, $0.50 cached input and $25.00 output; its changelog entry of September 8 states the same rates and date. No Hugin record states this date: the deadline board has carried it since September 27, and this row sits beside the September 27 record on OpenAI's September 22 prices, written from the same changelog. Does the pricing page still carry the date and the rates the day after, and does it say billing began?
    Instrument: Re-read the pricing page's Life Sciences row and its billing sentence, and quote both. ⚠ Access is limited to approved organisations in OpenAI's trusted-access program; this desk is not one and sees no bill, so the reading is what the page says, not whether anyone was charged. ⚠ The same page says GPT-5.6 Sol's promotional pricing is available 'at least through November 21, 2026' — a floor this row does not measure.
    Last instrument reading of the operative pages: 2 recorded terms present
  26. Past due — nothing filed
    Amazon's Bedrock legacy lifecycle table lists Anthropic's Claude Opus 4.1 (anthropic.claude-opus-4-1-20250805-v1:0) with a Legacy date of July 8, 2026, an end-of-life date of January 8, 2027 and a public extended access start date of October 8, 2026. The page says that in public extended access 'you should expect higher pricing, which will be set by the model provider', and that 'The model remains available until its EOL date.' The September 28 record lists what Opus 4.1 will cost on Bedrock from October 8 among the things it does not say, and found Bedrock's extended-access price table listing only two Claude 3.5 Sonnet models. Does the table still give October 8 as the start of public extended access the day after, does Bedrock publish an extended-access price for Opus 4.1, and is the end-of-life date still January 8, 2027?
    Instrument: Re-read the legacy table's Claude Opus 4.1 row and the page's extended-access rules, and quote them; check Bedrock's pricing page (https://aws.amazon.com/bedrock/pricing/) for an extended-access row naming Opus 4.1. ⚠ Extended access changes a price, not availability: nothing is due to disappear on October 8, and a date moved later is 'moved', never 'missed'. ⚠ Bedrock's pricing page renders most prices by script (its extended-access table read as text on September 28), and this desk holds no AWS account and sees no bill or customer notice, so a price absent from the page is a reading of the page, not proof that no price changed. ⚠ Amazon says its dates 'may differ from dates published by model providers (such as Anthropic or Cohere)'; Anthropic's own API deprecation page is a different platform and is context, not evidence, for this row. ⚠ Disclosure: Anthropic makes Claude Opus 4.1 and the Claude models that help draft Hugin records; this row is read to the same standard as every other provider's. The model's end of life on January 8, 2027 is a separate row.
    Last instrument reading of the operative pages: 5 recorded terms present
  27. Past due — nothing filed
    OpenAI's Codex models page states that GPT-5.5 retires from ChatGPT, ChatGPT Work and Codex on all plans on October 14, 2026, while the retirement does not apply to the OpenAI API. The page now recommends GPT-6 Sol for paid plans and GPT-6 Luna on the desktop app for Free and Go plans, when available. Does the page still carry the date and scope the day after, and what plan-specific replacements does it name then?
    Instrument: Re-read the Codex models page's retirement notice, model card and migration guidance. Record the date, surfaces, API exception, and current plan-specific replacement ids. ⚠ The instrument is the page, not a request: a retired name can be served quietly by its replacement, so a successful call proves nothing about scope. ⚠ The same page's GPT-5.4 line ('retire from Codex on August 31, 2026') was still in the future tense two weeks after its own date — check whether this one moves.
    Last instrument reading of the operative pages: 4 recorded terms present · 1 term the page repeats 6+ times — presence here may not be about this record
  28. Past due — nothing filed
    Amazon's Bedrock legacy lifecycle table lists Anthropic's Claude Sonnet 4 (anthropic.claude-sonnet-4-20250514-v1:0) in 23 Regions with a Legacy date of April 14, 2026, a public extended access start date of July 14, 2026 and an end-of-life date of October 14, 2026, and its model card states 'Model EOL date: October 14, 2026'. The page says that on or soon after an end-of-life date requests to the model 'will fail' unless privately arranged, and the table has no replacement column. No Hugin record states this date: the September 28 record cites this table for other dates, and this row was filed the same day after the uncovered-dates audit read Sonnet 4's date there. Does the table still list October 14 the day after, does the model card mark the model end of life, and does any page name a successor?
    Instrument: Re-read the legacy table's Claude Sonnet 4 row and the model card, and quote the dates and the lifecycle label. ⚠ Amazon says requests fail 'on, or soon after' the date, so a model still listed the day after is not a missed date, and a later date is 'moved'. ⚠ The table says it leaves out models already past end of life, yet on September 28 it still listed Nova Premier, Nova Sonic and Claude 3 Haiku after their dates: a row still there after October 14 is a reading of the page, and a row gone is not proof either. ⚠ The model card labels the lifecycle 'Legacy (certain regions)' without naming them, while the table's row gives one date for all 23 Regions it lists; a Region-by-Region change is a change to quote. ⚠ Amazon says its dates may differ from those model providers publish; Anthropic's own API deprecation page is a different platform and is context, not evidence, for this row. ⚠ Disclosure: Anthropic makes Claude Sonnet 4 and the Claude models that help draft Hugin records; this row is read to the same standard as every other provider's. This desk holds no AWS account and calls no model.
    Last instrument reading of the operative pages: 5 recorded terms present
  29. Past due — nothing filed
    Microsoft's Foundry retirement schedule, last updated September 21, 2026, lists sora-2 version 2025-12-08, a Preview model, for retirement on October 15, 2026 with '—' in the Replacement column, three weeks after OpenAI shut its own Sora 2 API. Microsoft's lifecycle page says Preview models launch with a 'not sooner than' retirement date and 'are sometimes extended beyond that initial window'. Does the schedule still list October 15 the day after, was the date extended, does it name a replacement, and does it mark the model retired?
    Instrument: Re-read the schedule's Azure OpenAI table and quote both sora-2 rows. ⚠ A Preview date is a floor Microsoft says it sometimes extends: a later date on the day is 'moved', never 'missed'. ⚠ This desk cannot test Azure deployments or see the 30-day notice Microsoft's policy promises when no replacement exists, so a row marked Retired is a reading of the page, not proof that inference returns 410 Gone. ⚠ OpenAI's own Sora 2 shutdown is a different platform and is filed on its own row.
    Last instrument reading of the operative pages: 2 recorded terms present
  30. Past due — nothing filed
    GitHub's changelog post of September 18, 2026 states it will deprecate Gemini 3.7 Flash, GPT-5.5, GPT-5.4, GPT-5.4 mini, GPT-5 mini and Grok 4.5 across all GitHub Copilot experiences on October 19, 2026, with Gemini 3.8 Flash, GPT-5.6 Sol, GPT-5.6 Luna and Grok 4.6 as suggested alternatives that switch on automatically for Copilot Business and Enterprise customers unless an administrator has turned off the global default. As read on September 27, GitHub's own model retirement table listed none of the six. Does the notice still carry that date and those six models the day after, and does GitHub record the deprecation as done?
    Instrument: Re-read GitHub's 2026-09-18 changelog post and quote its table; re-read the 'Model retirement history' table on the supported-models docs page (https://docs.github.com/en/copilot/reference/ai-models/supported-models) for the six, which it did not list on September 27, and check the changelog index for a follow-up retirement post. ⚠ A model still listed as GA in the docs after the date is a documentation lag to report, not proof the deprecation did not execute: this desk holds no Copilot seat and calls no model. ⚠ The October 22 feature-default policy in the same record is a separate term; this row does not measure it.
    Last instrument reading of the operative pages: 7 recorded terms present
  31. Past due — nothing filed
    Google Cloud's model-versions page for Gemini Enterprise Agent Platform, last updated September 25, 2026, lists gemini-2.5-pro, gemini-2.5-flash and gemini-2.5-flash-lite with a retirement date of October 20, 2026, under the page's rule that retirement timelines may be extended but will not be moved earlier than listed. The same page read October 16 in its July 9 version. Does it still list October 20 for all three the day after, was the date extended, and does it say the models were retired?
    Instrument: Re-read the model-versions page's 12-month table and quote the three gemini-2.5 rows and the extension rule. ⚠ Google says these dates may be extended but not brought forward: a later date on the day is 'moved', and because this desk calls no endpoint, a page still listing the models after October 20 is a reading of the page, not proof they still answer. ⚠ The Gemini API lists the same three models with 'No shutdown date announced'; that is a different platform and not what this row measures. docs.cloud.google.com answered curl carrying this desk's identifying user-agent with HTTP 200 on 2026-09-28T06:07Z; no browser user-agent was needed.
    Last instrument reading of the operative pages: 4 recorded terms present
  32. Past due — nothing filed
    Google Cloud's open model deprecations page for Gemini Enterprise Agent Platform, last updated September 25, 2026, lists sixteen open model endpoints offered as a service (MaaS), from deepseek-ocr-maas to qwen3-next-80b-a3b-thinking-maas, each deprecated July 21, 2026 and retiring October 21, 2026, with a self-deploy alternative on Model Garden and no managed replacement named. An Agent Platform release note dated July 21 announced the same sixteen. The September 27 record does not mention these endpoints or their date: the date was found after that record, by this desk reading Google's Agent Platform release notes. Does the page still list October 21 for all sixteen the day after, did any date or alternative change, does it name a managed replacement, and does it say the endpoints were retired?
    Instrument: Re-read the open model deprecations table and quote each endpoint's row and the page's definition of retirement; check the Agent Platform release notes (https://docs.cloud.google.com/gemini-enterprise-agent-platform/release-notes) for a later entry changing the date. ⚠ This desk calls no endpoint, so a page still listing an endpoint after October 21 is a reading of the page, not proof it still answers, and a row gone from the table is a change to quote, not proof of retirement. ⚠ Unlike the model-versions page, this page states no rule that its dates will not move earlier, so an earlier date is 'moved' as much as a later one. ⚠ The self-deploy alternatives run in the customer's own project, not as serverless endpoints; a managed replacement named later is a change to quote. docs.cloud.google.com answered curl carrying this desk's identifying user-agent with HTTP 200 on 2026-09-28.
    Last instrument reading of the operative pages: 17 recorded terms present
  33. Past due — nothing filed
    GitHub's Copilot docs say the 'Default policy for new features' policy for Copilot Business and Enterprise 'will start applying to new and existing GA features from October 22, 2026', that 'This policy is enabled by default', and that 'If you don't take action, unconfigured features will be enabled on October 22.' The September 24 changelog post says 'Starting October 22, the policy takes effect.' Does GitHub still carry October 22 the day after, does the docs page say the policy is active, and did the default change?
    Instrument: Re-read the docs page's 'Default availability of features' section and the September 24 changelog post, and quote the date sentences. ⚠ On September 28 the docs described the policy as 'not currently active'; after October 22, date sentences rewritten in the past tense are the expected change, and a lost term is a prompt to quote the new wording, not a finding by itself. ⚠ This desk holds no Copilot Business or Enterprise seat and cannot see any administrator's settings: the reading is what GitHub's pages say, not whether a feature switched on in any account. ⚠ The October 19 model deprecation in the same record is a separate row.
    Last instrument reading of the operative pages: 1 recorded term present · 3 no longer found
  34. Past due — nothing filed
    Google's Gemini API deprecations page, in the revision its footer stamps 'Last updated 2026-10-01 UTC', lists three Veo 3.1 preview video models — veo-3.1-lite-generate-preview (released March 31, 2026), veo-3.1-generate-preview and veo-3.1-fast-generate-preview (both released October 15, 2025) — with a shutdown date of October 22, 2026 and gemini-omni-1.1-flash as the recommended replacement, under the page's caveat that listed dates are 'the earliest possible dates on which a model might be retired'. The Internet Archive's September 26 copy of the page listed all three with 'No shutdown date announced'. The page says deprecation announcements are made on the release notes page, and the Gemini API changelog carried no entry announcing a shutdown for any of the three when read on September 30. No Hugin record states this date: the uncovered-commitments audit found it on the page this desk watches for the gemini-omni-flash-preview row, and this row sits beside the September 13 record that reported that endpoint's date. Does the table still list October 22 and the same replacement for all three the day after, does the changelog ever announce it, and does the page say the models were shut down?
    Instrument: Re-read the deprecations table's Veo models section and quote the three veo-3.1 preview rows; check the Gemini API changelog (https://ai.google.dev/gemini-api/docs/changelog) for an entry announcing them. ⚠ An earliest possible date: a model still answering on October 23 is NOT a missed date — file it as the page reads, never as a failure the provider did not promise; a later date is 'moved'. ⚠ The replacement is not a newer Veo: the table names gemini-omni-1.1-flash, Google's Gemini Omni Flash model, for all three, so the migration is a change of model, not of id. ⚠ The page says already-shutdown models are grayed, yet the revision that added this date deleted the gemini-omni-flash-preview row outright: a Veo row gone after October 22 is a reading of the page, not proof of a shutdown. This desk calls no endpoint. ai.google.dev answered curl carrying this desk's identifying user-agent with HTTP 200 at 2026-10-01T05:23Z.
    Last instrument reading of the operative pages: 4 recorded terms present · 1 no longer found
  35. Past due — nothing filed
    Seventeen rows retire on October 23, 2026 — the heaviest date on the ledger, and the one carrying gpt-4-turbo, gpt-4, o1, o1-pro, o4-mini and gpt-image-1. Does that schedule survive to the day after intact, or does any row on it move?
    Instrument: Re-read the ledger's 2026-04-22 section — two tables, twelve snapshot rows and five fine-tune base-model rows — and quote the dated ids. ⚠ This date is printed as 'October 23, 2026' rather than in the ISO form the September rows use, so a reader normalising by format alone will miss it; the strings watched here are ids, not dates.
    Last instrument reading of the operative pages: 3 recorded terms present
  36. Past due — nothing filed
    Google's October 8 Gemini API changelog says deep-research-pro-preview-12-2025 will shut down October 23, 2026 and names deep-research-preview-04-2026 or deep-research-max-preview-04-2026 as migration targets. The deprecations table qualifies listed dates as earliest possible. On October 24, do the pages still carry that schedule and those instructions, and does Google state that retirement occurred?
    Instrument: Re-read the October 8 changelog entry and the deprecations table's named Deep Research row. Compare the identifier, date, migration parameter and replacements. Record page changes as page readings. No endpoint test is authorized by this check: an unchanged announcement, removed row or earliest-possible date alone does not establish shutdown. Quote a later provider statement separately if it says retirement occurred; no resolution is filed automatically.
    Last instrument reading of the operative pages: 4 recorded terms present
  37. Past due — nothing filed
    OpenAI's custom GPT retirement and migration FAQ lists 'Oct 26, 2026 (planned): Creation of new custom GPTs ends' among the milestones for affected Enterprise workspaces, which it says are subject to change, tells readers to publish any drafts they need to migrate before this cutoff, and says the creation freeze does not prevent edits to existing, unmigrated GPTs. The Internet Archive's September 18 copy of the same FAQ gave September 25 for this cutoff, and no release note records the move. Does the FAQ still carry October 26 the day after, and does it say creation of new custom GPTs ended?
    Instrument: Re-read the FAQ's Enterprise milestone list and quote the creation-cutoff line. ⚠ The cutoff has moved once already (September 25 to October 26) without a release note, so a changed date is found only by re-reading. ⚠ The page is the instrument: this desk holds no ChatGPT Enterprise workspace and cannot test whether creating a GPT is refused, so a page that says creation ended is a reading of the page, not an observation of the product. ⚠ help.openai.com refuses node fetch and answers curl on the same identifying user-agent only some of the time; an unread page is a limit of this desk, never a pass.
    Last instrument reading of the operative pages: 2 recorded terms present
  38. Past due — nothing filed
    OpenAI's deprecations ledger says existing evals become read-only on October 31, 2026. Does the ledger still carry that stage on the day after, and did the read-only transition happen on the date it names?
    Instrument: Re-read the deprecations ledger and quote the Evals rows it carries. A read-only transition is not provable by absence from a public page -- nothing disappears when a product stops accepting writes -- so this row asks the narrower question the page can actually settle: does it still say this.
    Last instrument reading of the operative pages: 2 recorded terms present
  39. Past due — nothing filed
    Mistral's changelog entry of September 29, 2026 says 'Z.ai GLM 5.2 (zai-glm-5-2) is deprecated and retires on October 31, 2026. Use Z.ai GLM 5.3 (zai-glm-5-3) instead, at the same price.', the day after its September 28 entry made Z.ai GLM 5.3 generally available, and Mistral's models page lists zai-glm-5-2 in its 'Deprecated & retired models' table with deprecation 9/29/2026, retirement 10/31/2026 and Z.ai GLM 5.3 as the alternative. No Hugin record states this date: the uncovered-commitments audit found it on the changelog this desk watches for the Leanstral 1.5 row, and this row sits beside the September 28 record that reported Leanstral's date. Does the changelog still carry October 31 and the same replacement the day after, and does the models page show the model retired?
    Instrument: Re-read the changelog's September 29 entry and quote its GLM 5.2 sentence; re-read the models page's 'Deprecated & retired models' table and quote the zai-glm-5-2 row. ⚠ 'At the same price' is Mistral's statement; this desk did not compare the two models on Mistral's pricing page. ⚠ This desk holds no Mistral key and cannot call the endpoint, so a retirement on the pages is a reading of the pages, never an observation that requests fail. ⚠ This row measures Mistral's API only; Z.ai's own platform is a different provider and not what it reads.
    Last instrument reading of the operative pages: 3 recorded terms present
  40. Past due — nothing filed
    xAI's migration guide, published September 2, 2026, retires the grok-imagine-image-quality model slug on November 2, 2026 while keeping it resolving — requests are served by grok-imagine-image-2.0 at low quality, at a different price. Does the guide still carry that date and that redirect the day after, or does the name stop resolving?
    Instrument: Re-read the migration guide and quote its effective date and its redirect sentence. ⚠ A silent redirect cannot be confirmed by an error: the reading is the page's own statement of what answers the retired name, not whether a call still succeeds.
    Last instrument reading of the operative pages: 3 recorded terms present · 2 terms the page repeats 6+ times — presence here may not be about this record
  41. Upcoming
    Google's Gemini API deprecations table, read October 7, gives five preview models one shutdown date of November 17, 2026 — the speech previews gemini-3.1-flash-tts-preview, gemini-2.5-flash-preview-tts and gemini-2.5-pro-preview-tts, replaced by gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts, and the live previews gemini-3.1-flash-live-preview and gemini-2.5-flash-native-audio-preview-12-2025, replaced by gemini-3.8-live. Do all five rows still read the same the day after?
    Instrument: Re-read the deprecations table and quote all five rows. ⚠ Earliest possible dates again: a preview still answering on November 18 is not a missed date. ⚠ Five ids on one date, so a partial change is the interesting reading — report each id separately rather than one verdict for the group.
    Last instrument reading of the operative pages: 5 recorded terms present
  42. Upcoming
    Google Cloud's Gemini Enterprise Agent Platform lists gemini-3.6-flash (released July 21, 2026) with a retirement date of November 19, 2026 and gemini-3.8-flash as its replacement, in a table of models 'available for shorter availability periods' that promises at least 45 days between posting a date and the retirement. Does the row still read the same the day after?
    Instrument: Re-read the short-term availability table and quote the gemini-3.6-flash row. ⚠ Google Cloud's rule is the opposite of the Gemini API's: a posted retirement date can be extended but not moved earlier, so this date is a ceiling on the earliest, not a floor. An extension is 'moved', not 'missed'. ⚠ The Gemini API's deprecations page is a separate clock and does not settle this row.
    Last instrument reading of the operative pages: 2 recorded terms present · 1 term the page repeats 6+ times — presence here may not be about this record
  43. Upcoming
    OpenAI's API pricing page states 'GPT-5.6 Sol’s promotional pricing is available at least through November 21, 2026.' and lists gpt-5.6-sol, in its 'Cyber models' table, at $4.00 input, $0.40 cached input, $5.00 cache writes and $20.00 output per 1M short-context tokens. 'At least through' is a floor: the promotion is stated to last at least through November 21, and after that it may end or continue; the page does not say what the price becomes. The September 27 record reports the sentence and calls it 'a floor, not an end date'. Did the promotional price hold through November 21, and the day after, does the page carry the same sentence, a later date, a new gpt-5.6-sol price, or a statement that the promotion ended?
    Instrument: Re-read the pricing page's promotional sentence and the gpt-5.6-sol row, and quote both; check OpenAI's API changelog (https://developers.openai.com/api/docs/changelog), whose August 21 entry set the $4/$20 price, for a later entry. ⚠ The date is a floor, so the verdict runs one way: a price rise dated before November 21 would be 'missed'; the promotion holding through November 21 is 'kept', whether it then ends or continues; the sentence rewritten with a later date is 'moved', never 'missed'. ⚠ The page names no price for after the promotion; this desk's August 7 reading recorded $5.00/$30.00, a figure of this desk's, not the page's. ⚠ The flagship table's gpt-5.6-sol row is not in the page's served text (it sits in a collapsed, script-rendered table), so this row watches the 'Cyber models' row, and that row gone from the text is a change to quote, not proof of a price change. This desk makes no billed API calls and sees no invoice.
    Last instrument reading of the operative pages: 2 recorded terms present
  44. Upcoming
    Amazon's Bedrock legacy lifecycle table lists AI21 Labs' Jamba 1.5 Large (ai21.jamba-1-5-large-v1:0) and Jamba 1.5 Mini (ai21.jamba-1-5-mini-v1:0), both in us-east-1, with a Legacy date of May 26, 2026, a public extended access start date of August 26, 2026 and an end-of-life date of November 26, 2026, and both model cards state 'Model EOL date: November 26, 2026'. The page says that on or soon after an end-of-life date requests to the model 'will fail' unless privately arranged, and the table has no replacement column. No Hugin record states this date: the September 28 record cites this table for other dates, and this row was filed the same day after the uncovered-dates audit read the Jamba date there. One row carries both models because the table gives them one date. Does the table still list November 26 for both the day after, do the model cards mark them end of life, and does any page name a successor?
    Instrument: Re-read the legacy table's two Jamba 1.5 rows and both model cards, and quote the dates and lifecycle labels. ⚠ Amazon says requests fail 'on, or soon after' the date, so a model still listed the day after is not a missed date, and a later date is 'moved'. ⚠ The table says it leaves out models already past end of life, yet on September 28 it still listed Nova Premier, Nova Sonic and Claude 3 Haiku after their dates: a row still there after November 26 is a reading of the page, and a row gone is not proof either. ⚠ If the two models' dates part, each is quoted and filed on its own. This desk holds no AWS account and calls no model.
    Last instrument reading of the operative pages: 7 recorded terms present
  45. Upcoming
    The v1/prompts API and reusable prompt objects are scheduled to shut down on November 30, 2026. Does that happen on the stated date, move, or pass without a provider record?
    Instrument: Re-read the deprecations ledger's reusable-prompts section. An absence check against the API reference was considered and NOT filed: this desk has not established which string on that reference would disappear, and pinning one unverified would be a check whose failure mode is unknown.
    Last instrument reading of the operative pages: 1 recorded term present
  46. Upcoming
    Google's Gemini API pricing page lists every paid per-token rate on gemini-4-argon at one price 'through November 30, 2026' and at exactly twice that price 'starting December 1, 2026'. Does the step take effect as listed, move, or change in silence?
    Instrument: Read the Gemini API pricing page for gemini-4-argon and quote both Standard lines, input and output. The day after, a page still listing $2.00 input on December 1 is 'moved' or 'reversed', never 'kept'. ⚠ This desk calls no endpoint and sees no invoice: the reading is Google's listed price, not what any account was billed. ⚠ Only per-token rates step; the grounding charges carry no dated second figure.
    Last instrument reading of the operative pages: 2 recorded terms present
  47. Upcoming
    Amazon's Bedrock legacy lifecycle table lists TwelveLabs' Marengo Embed v2.7 (twelvelabs.marengo-embed-2-7-v1:0) in ap-northeast-2, eu-west-1 and us-east-1 with a Legacy date of May 29, 2026, a public extended access start date of August 29, 2026 and an end-of-life date of November 30, 2026, and its model card states 'Model EOL date: November 30, 2026'. The page says that on or soon after an end-of-life date requests to the model 'will fail' unless privately arranged, and the table has no replacement column. No Hugin record states this date: the September 28 record cites this table for other dates, and this row was filed the same day after the uncovered-dates audit read Marengo's date there. Does the table still list November 30 the day after, does the model card mark the model end of life, and does any page name a successor?
    Instrument: Re-read the legacy table's Marengo Embed v2.7 row and the model card, and quote the dates and the lifecycle label. ⚠ Amazon says requests fail 'on, or soon after' the date, so a model still listed the day after is not a missed date, and a later date is 'moved'. ⚠ The table says it leaves out models already past end of life, yet on September 28 it still listed Nova Premier, Nova Sonic and Claude 3 Haiku after their dates: a row still there after November 30 is a reading of the page, and a row gone is not proof either. ⚠ On September 28 the model card's availability table listed us-east-1 and eu-west-1 only, where the legacy table also lists ap-northeast-2; a Region-by-Region change is a change to quote. ⚠ Bedrock's model card index also carries a Marengo Embed 3.0 card, which no page read here calls the replacement; one named later is a change to quote. This desk holds no AWS account and calls no model.
    Last instrument reading of the operative pages: 4 recorded terms present
  48. Upcoming
    Anthropic's model deprecations page lists claude-sonnet-4-5-20250929 as Deprecated on September 30, 2026 with a 'Tentative retirement date' of November 30, 2026, and its September 30 history entry says Anthropic notified developers 'of its upcoming retirement on the Claude API', naming claude-sonnet-5-5 as the recommended replacement. The page says its dates apply to Anthropic-operated platforms (the Claude API, Claude Platform on AWS and Microsoft Foundry) and that Amazon Bedrock and Google Cloud set their own schedules. The October 10 record reports the November 30 date beside Bedrock's own, separately. The day after, does the page still give November 30, 2026, does it mark the model retired, and is the replacement still claude-sonnet-5-5?
    Instrument: Re-read the status table's claude-sonnet-4-5-20250929 row and the September 30 history entry, and quote both. ⚠ The page calls the date 'tentative': a later date is 'moved', never 'missed', and a model still listed as Deprecated on December 1 is a reading of the page, not proof that requests still succeed — this desk calls no model and holds no API account. ⚠ Retired means retired on Anthropic-operated platforms only; Bedrock's own April 8, 2027 date is a separate row, and the two are never combined. ⚠ Disclosure: Anthropic makes Claude Sonnet 4.5 and the Claude models that help draft Hugin records; this row is read to the same standard as every other provider's.
    Last instrument reading of the operative pages: 4 recorded terms present
  49. Upcoming
    Were gpt-image-1-mini, gpt-image-1.5 and the chatgpt-image-latest alias removed from the API on December 1, as the deprecations ledger scheduled on June 2?
    Instrument: Re-read the deprecations ledger, which is the one OpenAI page this desk can mechanically read. The ledger states the schedule and goes on stating it afterwards, so this row can confirm the commitment was published and dated — it cannot, by itself, prove the removal executed.
    Last instrument reading of the operative pages: 3 recorded terms present
  50. Upcoming
    Three GPT-5 snapshots -- gpt-5-2025-08-07, gpt-5-mini-2025-08-07 and gpt-5-nano-2025-08-07 -- are scheduled for removal from the API on December 11, 2026. Does the ledger still carry that schedule the day after, and can this desk establish the removal at all?
    Instrument: Re-read the ledger's GPT-5 and o3 section and quote the dated rows. ⚠ The second half of the 2026-08-10 check -- confirming the ids left the live models list -- is NOT available here: measured 2026-08-31, all three are already absent from that list, because it names aliases rather than dated snapshots. Establishing this removal needs a source that lists snapshots, and this desk does not have one.
    Last instrument reading of the operative pages: 3 recorded terms present
  51. Upcoming
    OpenAI's custom GPT retirement and migration FAQ states that custom GPTs are scheduled to retire on December 11, 2026, that the transition affects all ChatGPT plans, and that at the applicable retirement date custom GPTs and their GPT pages become inaccessible; Enterprise workspaces with a qualified, approved deferral get until February 11, 2027. The FAQ has already been rewritten once, moving two Enterprise dates, with no release note. Does it still carry the December 11 date the day after, and does it say the retirement happened?
    Instrument: Re-read the FAQ's answer to 'When are custom GPTs retiring?' and its Enterprise milestones, and quote both. ⚠ The FAQ keeps no list of its own changes and moved the Enterprise creation cutoff and migration target between September 16 and September 25 without a release note (the record compares Internet Archive copies of September 17, 18 and 25), so a changed date is found only by re-reading. ⚠ The page is the instrument: this desk holds no ChatGPT account and cannot see the in-product notices or admin emails the FAQ says govern account-specific timing. ⚠ help.openai.com refuses node fetch and answers curl on the same identifying user-agent only some of the time; an unread page is a limit of this desk, never a pass.
    Last instrument reading of the operative pages: 4 recorded terms present
  52. Upcoming
    Google Cloud's model-versions page for Gemini Enterprise Agent Platform, last updated September 25, 2026, lists gemini-live-2.5-flash-native-audio, released December 12, 2025, with a retirement date of December 13, 2026 and an empty replacement column, under the page's rule that retirement timelines may be extended but will not be moved earlier than listed. The September 27 record does not mention this model or its date: the date was found by the uncovered-commitments audit reading the page this desk watches for the gemini-2.5 retirement. Does the page still list December 13 the day after, was it extended, does it name a replacement, and does it say the model was retired?
    Instrument: Re-read the model-versions page's 12-month table and quote the gemini-live-2.5-flash-native-audio row and the extension rule. ⚠ Google says these dates may be extended but not brought forward: a later date on the day is 'moved', and because this desk calls no endpoint, a page still listing the model after December 13 is a reading of the page, not proof it still answers. ⚠ The table's replacement cell for this model was empty on September 27; a replacement named later is a change to quote, not an error. docs.cloud.google.com answered curl carrying this desk's identifying user-agent with HTTP 200 on 2026-09-28T06:15Z.
    Last instrument reading of the operative pages: 2 recorded terms present
  53. Upcoming
    Google's Gemini API changelog, in its August 13, 2026 GA entry, says Gemini 3.7 Flash is available at an introductory price through December 31, 2026 — without stating the introductory or the standard price. Does the window end as stated, extend, or change in silence, and does any Google page ever state the price it steps to?
    Instrument: Re-read the changelog's 2026-08-13 entry and quote its sentence; read the Gemini API pricing page for gemini-3.7-flash. ⚠ The changelog names a date and NO price, so 'the window ended' is only half a reading until a page states what the price became. Since September 28 the pricing page is watched as well: it lists the paid Standard input price for gemini-3.6-flash, gemini-3.7-flash and gemini-3.8-flash as '$0.75 through December 31, 2026.' then '$1.50 starting January 1, 2027.', and output as '$3.75' then '$7.50', so the day after, quote both lines for 3.7 Flash. A page still listing $0.75 on January 1 is 'moved' or 'reversed', never 'kept'. ⚠ This desk calls no endpoint and sees no invoice: the reading is Google's listed price, not what any account was billed. ⚠ Since October 8 Google routes every gemini-3.7-flash request to gemini-3.8-flash and the pricing page carries no 3.7 Flash section: quote 3.8 Flash's two lines, say so, and say that no page read states which rate bills a routed request.
    Last instrument reading of the operative pages: 8 recorded terms present · 2 terms the page repeats 6+ times — presence here may not be about this record
  54. Upcoming
    On January 6, 2027 the customers who can still create fine-tuning jobs lose that, while inference on already-trained models is stated to continue until the underlying base model is deprecated. Does the ledger still carry both halves of that sentence the day after?
    Instrument: Re-read the ledger's fine-tuning section and quote its Date/Update rows. ⚠ The second half is the load-bearing half: this row's date is NOT when a fine-tuned model stops answering — that is its base model's own date, and five fine-tune base models retire on 2026-10-23, ten weeks earlier. Watch the conditional sentence, not the headline date.
    Last instrument reading of the operative pages: 2 recorded terms present
  55. Upcoming
    A section dated 2026-10-01 says four text-to-speech ids — tts-1, tts-1-hd, gpt-4o-mini-tts-2025-03-20 and gpt-4o-mini-tts-2025-12-15 — are deprecated and will be removed from the API on January 6, 2027, all four pointing at gpt-realtime-2.1-mini. Does the ledger still carry that date and that single replacement the day after, and are the four ids gone from it?
    Instrument: Re-read the ledger's '2026-10-01: Text-to-speech models' section and quote its sentence and its four table rows. ⚠ The section says 'at least three months' notice' — a FLOOR, not a figure, and not the same claim as the other section's flat 'six months'. A later re-read must not quietly convert one into the other. ⚠ Four ids, not all text-to-speech: this row is the four the section lists.
    Last instrument reading of the operative pages: 4 recorded terms present · 1 term the page repeats 6+ times — presence here may not be about this record
  56. Upcoming
    Amazon's Bedrock legacy lifecycle table lists Anthropic's Claude Opus 4.1 (anthropic.claude-opus-4-1-20250805-v1:0) in us-east-1, us-east-2 and us-west-2 with an end-of-life date of January 8, 2027, after public extended access from October 8, 2026, and its model card states 'Model EOL date: January 8, 2027'. The page says that on or soon after an end-of-life date requests to the model 'will fail' unless privately arranged, and the table has no replacement column. No Hugin record states this date: the September 28 record reports the table's October 8 extended-access date for Opus 4.1, which has its own row, but not its end of life, and this row was filed the same day after the uncovered-dates audit read the date there. Does the table still list January 8, 2027 the day after, does the model card mark the model end of life, and does any page name a successor?
    Instrument: Re-read the legacy table's Claude Opus 4.1 row and the model card, and quote the dates and the lifecycle label. ⚠ Amazon says requests fail 'on, or soon after' the date, so a model still listed the day after is not a missed date, and a later date is 'moved'. ⚠ The table says it leaves out models already past end of life, yet on September 28 it still listed Nova Premier, Nova Sonic and Claude 3 Haiku after their dates: a row still there after January 8 is a reading of the page, and a row gone is not proof either. ⚠ Amazon says its dates may differ from those model providers publish; Anthropic's own API deprecation page is a different platform and is context, not evidence, for this row. ⚠ Disclosure: Anthropic makes Claude Opus 4.1 and the Claude models that help draft Hugin records; this row is read to the same standard as every other provider's. This desk holds no AWS account and calls no model.
    Last instrument reading of the operative pages: 5 recorded terms present
  57. Upcoming
    Amazon's Bedrock legacy lifecycle table lists Anthropic's Claude Sonnet 4.5 (anthropic.claude-sonnet-4-5-20250929-v1:0) in 31 Regions with a Legacy date of October 8, 2026, a public extended access start date of January 8, 2027 and an end-of-life date of April 8, 2027. The page says that in public extended access 'you should expect higher pricing, which will be set by the model provider', and that the model remains available until its EOL date. The October 10 record reports the January 8 date. Does the table still give January 8, 2027 as the start of public extended access the day after, does Bedrock publish an extended-access price for Sonnet 4.5, and is the end-of-life date still April 8, 2027?
    Instrument: Re-read the legacy table's Claude Sonnet 4.5 row and the page's extended-access rules, and quote them; check Bedrock's pricing page (https://aws.amazon.com/bedrock/pricing/) for an extended-access row naming Sonnet 4.5. ⚠ Extended access changes a price, not availability: nothing is due to disappear on January 8, and a date moved later is 'moved', never 'missed'. ⚠ Bedrock's pricing page renders most prices by script, and this desk holds no AWS account and sees no bill or customer notice, so a price absent from the page is a reading of the page, not proof that no price changed. ⚠ Amazon says its dates may differ from dates published by model providers; Anthropic's own API deprecation page is a different platform and is context, not evidence, for this row. ⚠ Disclosure: Anthropic makes Claude Sonnet 4.5 and the Claude models that help draft Hugin records; this row is read to the same standard as every other provider's. The model's end of life on April 8, 2027 is a separate row.
    Last instrument reading of the operative pages: 4 recorded terms present
  58. Upcoming
    Nine legacy audio, realtime and transcription ids are scheduled to be removed on January 20, 2027, under a notice published July 20, 2026. Does the ledger still carry that schedule the day after?
    Instrument: Re-read the ledger's 2026-07-20 section and quote its dated rows. ⚠ This group retires whole FAMILIES rather than dated snapshots — a floating id like gpt-realtime keeps working right up to the date with nothing in a caller's code naming a version that could warn them.
    Last instrument reading of the operative pages: 2 recorded terms present
  59. Upcoming
    Google Cloud's Gemini Enterprise Agent Platform lists gemini-3.7-flash (released August 13, 2026) with a retirement date of January 28, 2027 and gemini-3.8-flash as its replacement — the same successor it names for gemini-3.6-flash two months earlier. Does the row still read the same the day after?
    Instrument: Re-read the short-term availability table and quote the gemini-3.7-flash row. ⚠ A posted Cloud date can be extended but not pulled earlier. ⚠ Check gemini-3.8-flash's own row at the same time: on 2026-10-07 it carried no retirement date, and a successor acquiring one is what turns this migration into a second migration.
    Last instrument reading of the operative pages: 2 recorded terms present · 1 term the page repeats 6+ times — presence here may not be about this record
  60. Upcoming
    OpenAI's custom GPT retirement and migration FAQ states that for affected Enterprise workspaces with an approved deferral 'the retirement date is Feb 11, 2027', and lists 'Feb 11, 2027: Retirement for workspaces with a qualified, approved deferral', adding that the extension does not apply to every workspace and that standard admin emails use the standard dates. Every other plan retires on December 11, 2026, which has its own row. Does the FAQ still carry February 11, 2027 the day after, and does it say the deferred retirement happened?
    Instrument: Re-read the FAQ's answer to 'When are custom GPTs retiring?' and its Enterprise milestones, and quote both February 11, 2027 lines. ⚠ The deferral date first appeared in the September 16–25 rewrite that no release note mentions, so a changed date is found only by re-reading. ⚠ The page is the instrument: this desk holds no Enterprise workspace, cannot see which workspaces hold an approved deferral, and cannot observe whether their GPTs stopped working. ⚠ help.openai.com refuses node fetch and answers curl on the same identifying user-agent only some of the time; an unread page is a limit of this desk, never a pass.
    Last instrument reading of the operative pages: 2 recorded terms present
  61. Upcoming
    whisper-1 and the three gpt-4o transcription models are scheduled for removal on February 26, 2027 — the farthest date on the ledger. Does that schedule survive eighteen months of re-reads, and does the replacement pair it names stay the same?
    Instrument: Re-read the ledger's 2026-08-26 section and quote its four dated rows. ⭐ This is the longest-horizon row on the board and the one most likely to matter to somebody who never chose it: whisper-1 is embedded in shipped code as a default rather than a decision, so the useful check is whether the replacement pair still reads the same in a year, not only whether the date holds.
    Last instrument reading of the operative pages: 2 recorded terms present
  62. Upcoming
    The replacement for the row that moved. Google's Gemini API deprecations table, read October 7, lists gemini-2.5-flash-image with a shutdown date of March 15, 2027 and gemini-3.1-flash-lite-image as the replacement — the same date and the same replacement Google Cloud's Agent Platform has carried for this model since its September 14 release note. Does the row still read the same the day after, and does the pricing page ever catch up?
    Instrument: Re-read the deprecations table and quote the gemini-2.5-flash-image row, then read the pricing page's Gemini 2.5 Flash Image warning. ⚠ These are earliest possible dates, so a model still answering on March 16 is NOT a missed date. ⚠ This row exists because the date on this page already moved once; a THIRD value is the finding, not a surprise. ⚠ On 2026-10-07 the pricing page still read October 2, 2026 — if it still does on the day, say so rather than treating the table as the only page.
    Last instrument reading of the operative pages: 4 recorded terms present
  63. Upcoming
    Google Cloud's model-versions page for Gemini Enterprise Agent Platform, last updated September 25, 2026, lists gemini-2.5-flash-image, released October 2, 2025, with a retirement date of March 15, 2027 and gemini-3.1-flash-lite-image as its replacement. A September 14 Agent Platform release note says the date was 'extended from October 2, 2026'. On the Gemini API the same model id has an October 2, 2026 earliest shutdown and a different replacement, which has its own row. Does the Cloud page still list March 15, 2027 and the same replacement the day after, was the date extended again, and does it say the model was retired?
    Instrument: Re-read the model-versions page's image-model table and quote the gemini-2.5-flash-image row and the extension rule; check the Agent Platform release notes (https://docs.cloud.google.com/gemini-enterprise-agent-platform/release-notes) for a further date change. ⚠ The date has been extended once already, on September 14, and Google says Cloud dates may be extended but not brought forward, so a later date is 'moved'. ⚠ The Gemini API's October 2, 2026 date for the same id is a different platform and not what this row measures. ⚠ This desk calls no endpoint, so a page still listing the model after March 15 is a reading of the page, not proof it still answers.
    Last instrument reading of the operative pages: 2 recorded terms present
  64. Upcoming
    Google Cloud's model-versions page for Gemini Enterprise Agent Platform, last updated September 25, 2026, lists four embedding models with a retirement date of April 1, 2027: text-embedding-005 (released November 18, 2024), text-embedding-004 and text-multilingual-embedding-002 (both May 14, 2024) and multimodalembedding@001 (February 12, 2024), under the page's rule that retirement timelines may be extended but will not be moved earlier than listed. The September 27 record does not mention these models: the date was found by the uncovered-commitments audit reading the page this desk watches for the gemini-2.5 retirement. Does the page still list April 1, 2027 for all four the day after, was any date extended, does it name a replacement, and does it say they were retired?
    Instrument: Re-read the model-versions page's embeddings table and quote the four April 1, 2027 rows and the extension rule. ⚠ The replacement cells in that table did not read unambiguously as visible text on September 27 (gemini-embedding-2, released April 22, 2026, sits at the top of the same table), so this row claims no replacement; a replacement named against a specific model later is a change to quote. ⚠ Google says these dates may be extended but not brought forward: a later date is 'moved'. This desk calls no endpoint, so a page still listing a model after April 1 is a reading of the page, not proof it still answers. docs.cloud.google.com answered curl carrying this desk's identifying user-agent with HTTP 200 on 2026-09-28.
    Last instrument reading of the operative pages: 5 recorded terms present
  65. Upcoming
    A section dated 2026-10-01 says gpt-5.3-codex, gpt-5.4-nano and gpt-5.1 are deprecated and will be removed from the API on April 1, 2027, each with a named recommended replacement (gpt-6-sol or gpt-6-luna). Does the ledger still carry that date and those three replacements the day after, and are the three ids gone from it?
    Instrument: Re-read the ledger's '2026-10-01: GPT-5.3-Codex, GPT-5.1, GPT-5.4-Nano' section and quote its sentence and its three table rows. ⚠ Unlike the six rows the 09-07 record found, all three name a replacement, so the question here is the DATE holding, not whether there is anywhere to go. ⚠ This desk holds no OpenAI key and cannot call the endpoint; absence from the ledger is a reading of the page, never an observation that requests fail.
    Last instrument reading of the operative pages: 4 recorded terms present
  66. Upcoming
    Amazon's Bedrock legacy lifecycle table lists Anthropic's Claude Sonnet 4.5 (anthropic.claude-sonnet-4-5-20250929-v1:0) in 31 Regions with an end-of-life date of April 8, 2027, after public extended access from January 8, 2027, and its model card states 'Model EOL date: April 8, 2027'. The page says that on or soon after an end-of-life date requests to the model 'will fail' unless privately arranged, that migration will not happen automatically, and the table has no replacement column. The October 10 record reports the date. Does the table still list April 8, 2027 the day after, does the model card mark the model end of life, and does any page name a successor?
    Instrument: Re-read the legacy table's Claude Sonnet 4.5 row and the model card, and quote the dates and the lifecycle label. ⚠ Amazon says requests fail 'on, or soon after' the date, so a model still listed the day after is not a missed date, and a later date is 'moved'. ⚠ The table has gone on listing models after their dates (Nova Premier, Nova Sonic and Claude 3 Haiku on September 28): a row still there after April 8 is a reading of the page, and a row gone is not proof either. ⚠ The page says lifecycle state can differ by Region and that its Regions column lists only the Regions an announced date covers; a Region-by-Region change is a change to quote. ⚠ Amazon says its dates may differ from those model providers publish; Anthropic's own API deprecation page is a different platform and is context, not evidence, for this row. ⚠ Disclosure: Anthropic makes Claude Sonnet 4.5 and the Claude models that help draft Hugin records; this row is read to the same standard as every other provider's. This desk holds no AWS account and calls no model.
    Last instrument reading of the operative pages: 6 recorded terms present
  67. Upcoming
    Google's Gemini API deprecations table lists gemini-3.1-flash-lite (released May 7, 2026) with an earliest possible shutdown date of May 7, 2027 and gemini-3.5-flash-lite as its replacement. Does the row still read the same the day after?
    Instrument: Re-read the deprecations table and quote the gemini-3.1-flash-lite row. ⚠ An earliest possible date: a model still answering the day after is not a missed date.
    Last instrument reading of the operative pages: 2 recorded terms present · 1 term the page repeats 6+ times — presence here may not be about this record
  68. Upcoming
    Google's Gemini API deprecations table lists gemini-embedding-001 (released July 14, 2025) with an earliest possible shutdown date of May 14, 2028 and gemini-embedding-2 as its replacement — the longest-horizon row on this desk's calendar, and the one whose migration is not a rename: stored embeddings do not carry across models. Does the row still read the same the day after?
    Instrument: Re-read the deprecations table and quote the gemini-embedding-001 row. ⚠ An earliest possible date: a model still answering the day after is not a missed date.
    Last instrument reading of the operative pages: 2 recorded terms present · 1 term the page repeats 6+ times — presence here may not be about this record

Citations that no longer resolve

These addresses returned 404 or 410. The underlying record may still exist elsewhere; the citation as written does not reach it. Listing them publicly is the point — a source list nobody re-checks is decoration.

  1. data.sec.govHTTP 404
    https://data.sec.gov/submissions/
    U.S. Securities and Exchange Commission1 citation
  2. support.claude.comHTTP 404
    https://support.claude.com/en/articles/15400594-claude-cowork-june-2026-usage-promotion
    Anthropic Help Center1 citation

Records whose text changed since we last read them

Not yet measurable. Change detection needs two successful reads of the same record, so the first sweep only establishes baselines. This is reported as “no comparison available” rather than “nothing changed”, because those are different claims.

Read successfully 478

An automated request from Hugin's own infrastructure retrieved this record.

List the 478 records
  1. ai.google.devHTTP 200
    https://ai.google.dev/gemini-api/docs/changelog
    Google2 citations
  2. ai.google.devHTTP 200
    https://ai.google.dev/gemini-api/docs/deprecations
    Google5 citations
  3. ai.google.devHTTP 200
    https://ai.google.dev/gemini-api/docs/pricing
    Google (Gemini API docs)2 citations
  4. america.govHTTP 200
    https://america.gov/about
    U.S. General Services Administration (America.gov)1 citation
  5. america.govHTTP 200
    https://america.gov/privacy-policy
    U.S. General Services Administration (America.gov)1 citation
  6. america.govHTTP 200
    https://america.gov/terms
    U.S. General Services Administration (America.gov)2 citations
  7. api.congress.govHTTP 200
    https://api.congress.gov/
    Library of Congress1 citation
  8. api.fda.govHTTP 200
    https://api.fda.gov/device/enforcement.json?search=event_id:99671&limit=10
    U.S. Food and Drug Administration (openFDA)1 citation
  9. api.fiscaldata.treasury.govHTTP 200
    https://api.fiscaldata.treasury.gov/services/api/fiscal_service/v1/accounting/mts/mts_table_5
    U.S. Department of the Treasury, Bureau of the Fiscal Service1 citation
  10. api.usaspending.govHTTP 200
    https://api.usaspending.gov/docs/endpoints
    U.S. Department of the Treasury / USAspending.gov2 citations
  11. clerk.house.govHTTP 200
    https://clerk.house.gov/evs/2026/roll280.xml
    Office of the Clerk, U.S. House of Representatives1 citation
  12. democrats-judiciary.house.govHTTP 200
    https://democrats-judiciary.house.gov/sites/evo-subsites/democrats-judiciary.house.gov/files/evo-media-document/2026-01-31-raskin-to-blanche-doj-re-epstein-files.pdf
    U.S. House Committee on the Judiciary, Minority1 citation
  13. democrats-transportation.house.govHTTP 200
    https://democrats-transportation.house.gov/news/press-releases/after-18-month-investigation-chairs-defazio-and-larsen-release-final-committee-report-on-boeing-737-max
    U.S. House Committee on Transportation and Infrastructure1 citation
  14. deploymentsafety.openai.comHTTP 200
    https://deploymentsafety.openai.com/gpt-5-6
    OpenAI Deployment Safety1 citation
  15. deploymentsafety.openai.comHTTP 200
    https://deploymentsafety.openai.com/gpt-5-6-preview
    OpenAI Deployment Safety1 citation
  16. developers.openai.comHTTP 200
    https://developers.openai.com/api/docs/changelog
    OpenAI1 citation
  17. developers.openai.comHTTP 200
    https://developers.openai.com/api/docs/deprecations
    OpenAI6 citations
  18. developers.openai.comHTTP 200
    https://developers.openai.com/api/docs/models/sora-2
    OpenAI1 citation
  19. developers.openai.comHTTP 200
    https://developers.openai.com/api/docs/pricing
    OpenAI2 citations
  20. disclosures-clerk.house.govHTTP 200
    https://disclosures-clerk.house.gov/FinancialDisclosure
    Office of the Clerk, U.S. House of Representatives1 citation
  21. docs.aws.amazon.comHTTP 200
    https://docs.aws.amazon.com/bedrock/latest/userguide/model-lifecycle-legacy.html
    Amazon Web Services3 citations
  22. docs.cloud.google.comHTTP 200
    https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions
    Google2 citations
  23. docs.cloud.google.comHTTP 200
    https://docs.cloud.google.com/gemini-enterprise-agent-platform/release-notes
    Google2 citations
  24. docs.mistral.aiHTTP 200
    https://docs.mistral.ai/resources/changelogs
    Mistral AI2 citations
  25. docs.x.aiHTTP 200
    https://docs.x.ai/developers/faq/security
    xAI (SpaceXAI) developer docs1 citation
  26. docs.x.aiHTTP 200
    https://docs.x.ai/developers/migration/imagine-image-quality-nov-2
    xAI1 citation
  27. docs.x.aiHTTP 200
    https://docs.x.ai/developers/release-notes
    xAI (SpaceXAI) developer docs1 citation
  28. en.wikipedia.orgHTTP 200
    https://en.wikipedia.org/wiki/GPT-5.6
    Wikipedia1 citation
  29. files.gao.govHTTP 200
    https://files.gao.gov/reports/GAO-25-107653/index.html
    Government Accountability Office1 citation
  30. files.gao.govHTTP 200
    https://files.gao.gov/reports/GAO-26-107859/index.html
    Government Accountability Office1 citation
  31. github.blogHTTP 200
    https://github.blog/changelog/2026-09-03-upcoming-deprecation-of-selected-github-copilot-models
    GitHub1 citation
  32. github.blogHTTP 200
    https://github.blog/changelog/2026-09-10-mai-code-1-flash-deprecated
    GitHub1 citation
  33. github.blogHTTP 200
    https://github.blog/changelog/2026-09-18-upcoming-deprecation-of-selected-github-copilot-models-in-mid-october
    GitHub1 citation
  34. github.blogHTTP 200
    https://github.blog/changelog/2026-09-24-default-enablement-of-copilot-features-for-copilot-business-and-enterprise
    GitHub1 citation
  35. help.openai.comHTTP 200
    https://help.openai.com/en/articles/10291617-scheduled-tasks-in-chatgpt
    OpenAI Help Center1 citation
  36. help.openai.comHTTP 200
    https://help.openai.com/en/articles/20001152-what-to-know-about-the-sora-discontinuation
    OpenAI2 citations
  37. help.openai.comHTTP 200
    https://help.openai.com/en/articles/20001519-custom-gpt-retirement-and-migration-faq
    OpenAI1 citation
  38. help.openai.comHTTP 200
    https://help.openai.com/en/articles/6825453-chatgpt-release-notes
    OpenAI Help Center1 citation
  39. help.openai.comHTTP 200
    https://help.openai.com/en/articles/9624314-model-release-notes
    OpenAI Help Center1 citation
  40. huggingface.coHTTP 200
    https://huggingface.co/blog/agent-intrusion-technical-timeline
    Hugging Face1 citation
  41. huggingface.coHTTP 200
    https://huggingface.co/blog/security-incident-july-2026
    Hugging Face1 citation
  42. hugin.studioHTTP 200
    https://hugin.studio/blog/july-10-the-model-can-carry-more
    Hugin1 citation
  43. hugin.studioHTTP 200
    https://hugin.studio/blog/july-11-the-best-live-events-reduce-friction
    Hugin1 citation
  44. hugin.studioHTTP 200
    https://hugin.studio/blog/july-12-evidence-should-be-visible
    Hugin1 citation
  45. hugin.studioHTTP 200
    https://hugin.studio/blog/july-15-the-agent-subscription-scoreboard
    Hugin1 citation
  46. hugin.studioHTTP 200
    https://hugin.studio/blog/july-16-the-date-is-part-of-the-evidence
    Hugin1 citation
  47. hugin.studioHTTP 200
    https://hugin.studio/blog/july-18-a-sentence-is-not-a-settlement
    Hugin1 citation
  48. hugin.studioHTTP 200
    https://hugin.studio/blog/july-21-the-meter-came-back
    Hugin1 citation
  49. hugin.studioHTTP 200
    https://hugin.studio/blog/july-25-a-reset-is-a-receipt-not-a-clock
    Hugin1 citation
  50. hugin.studioHTTP 200
    https://hugin.studio/blog/july-26-three-trays-not-one-pile
    Hugin1 citation
  51. hugin.studioHTTP 200
    https://hugin.studio/blog/july-28-the-map-has-to-be-visible
    Hugin1 citation
  52. hugin.studioHTTP 200
    https://hugin.studio/blog/july-28-two-kinds-of-work-evidence
    Hugin1 citation
  53. hugin.studioHTTP 200
    https://hugin.studio/blog/july-30-the-record-i-did-not-check
    Hugin1 citation
  54. hugin.studioHTTP 200
    https://hugin.studio/blog/july-31-the-check-that-only-happened-because-someone-else-published
    Hugin1 citation
  55. hugin.studioHTTP 200
    https://hugin.studio/blog/july-4-codex-fable-and-the-build-window
    Hugin1 citation
  56. hugin.studioHTTP 200
    https://hugin.studio/blog/july-5-reddit-scan-recovery-and-public-desk
    Hugin1 citation
  57. hugin.studioHTTP 200
    https://hugin.studio/blog/july-6-case-desk-and-daily-receipts
    Hugin1 citation
  58. hugin.studioHTTP 200
    https://hugin.studio/blog/july-7-source-status-and-case-confidence
    Hugin1 citation
  59. hugin.studioHTTP 200
    https://hugin.studio/blog/july-8-case-source-desk-and-gpt56-watch
    Hugin1 citation
  60. hugin.studioHTTP 200
    https://hugin.studio/blog/july-8-smaller-source-doors
    Hugin1 citation
  61. hugin.studioHTTP 200
    https://hugin.studio/blog/july-9-codex-travels-with-the-chat
    Hugin1 citation
  62. hugin.studioHTTP 200
    https://hugin.studio/blog/july-9-launch-day-discipline
    Hugin1 citation
  63. hugin.studioHTTP 200
    https://hugin.studio/news/july-10-daily-case-desk
    Hugin1 citation
  64. hugin.studioHTTP 200
    https://hugin.studio/news/july-10-gpt56-scheduled-work-and-limits
    Hugin1 citation
  65. hugin.studioHTTP 200
    https://hugin.studio/news/july-11-go-fest-and-daily-desk
    Hugin1 citation
  66. hugin.studioHTTP 200
    https://hugin.studio/news/july-12-go-fest-sunday-field-card
    Hugin1 citation
  67. hugin.studioHTTP 200
    https://hugin.studio/news/july-15-agent-capacity-ledger
    Hugin1 citation
  68. hugin.studioHTTP 200
    https://hugin.studio/news/july-16-ai-receipts-claude-for-teachers
    Hugin1 citation
  69. hugin.studioHTTP 200
    https://hugin.studio/news/july-18-ai-receipts-self-measured-claims
    Hugin1 citation
  70. hugin.studioHTTP 200
    https://hugin.studio/news/july-21-ai-control-receipts
    Hugin1 citation
  71. hugin.studioHTTP 200
    https://hugin.studio/news/july-25-opus-5-and-reset-receipts
    Hugin1 citation
  72. hugin.studioHTTP 200
    https://hugin.studio/news/july-26-daily-desk-ai-products-and-fraud-records
    Hugin1 citation
  73. hugin.studioHTTP 200
    https://hugin.studio/news/july-28-control-room-source-lanes
    Hugin1 citation
  74. hugin.studioHTTP 200
    https://hugin.studio/news/july-28-work-frontier-and-fraud-risk-records
    Hugin1 citation
  75. hugin.studioHTTP 200
    https://hugin.studio/news/july-30-the-five-hour-limit-came-back-on-schedule
    Hugin1 citation
  76. hugin.studioHTTP 200
    https://hugin.studio/news/july-31-two-labs-lost-containment-and-both-wrote-it-down
    Hugin1 citation
  77. hugin.studioHTTP 200
    https://hugin.studio/news/july-4-codex-fable-release-receipts
    Hugin1 citation
  78. hugin.studioHTTP 200
    https://hugin.studio/news/july-5-reddit-scan-recovery-receipts
    Hugin1 citation
  79. hugin.studioHTTP 200
    https://hugin.studio/news/july-6-case-index-receipts
    Hugin1 citation
  80. hugin.studioHTTP 200
    https://hugin.studio/news/july-7-fable-code-limit-extension
    Hugin1 citation
  81. hugin.studioHTTP 200
    https://hugin.studio/news/july-7-source-status-case-pulse
    Hugin1 citation
  82. hugin.studioHTTP 200
    https://hugin.studio/news/july-8-fable-code-court-records
    Hugin1 citation
  83. hugin.studioHTTP 200
    https://hugin.studio/news/july-8-gpt56-case-source-desk
    Hugin1 citation
  84. hugin.studioHTTP 200
    https://hugin.studio/news/july-9-gpt56-codex-chatgpt-observation
    Hugin1 citation
  85. hugin.studioHTTP 200
    https://hugin.studio/news/july-9-gpt56-general-availability-record
    Hugin1 citation
  86. hugin.studioHTTP 200
    https://hugin.studio/news/july-9-gpt56-launch-day-receipts
    Hugin1 citation
  87. hugin.studioHTTP 200
    https://hugin.studio/news/september-1-three-windows-one-false-pass
    Hugin1 citation
  88. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-a-billion-in-ssi
    Hugin1 citation
  89. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-an-ai-trading-ponzi
    Hugin1 citation
  90. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-billions-in-mitigation-unawarded
    Hugin1 citation
  91. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-canceled-in-your-name
    Hugin1 citation
  92. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-copilot-drops-six-models
    Hugin1 citation
  93. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-custom-gpts-retire-december-11
    Hugin1 citation
  94. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-eight-hundred-seventy-thousand-more-borrowers
    Hugin1 citation
  95. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-eleven-recalls-and-a-cord-rule
    Hugin1 citation
  96. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-eleven-warehouses
    Hugin1 citation
  97. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-gemini-2-5-two-clocks
    Hugin1 citation
  98. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-shut-down-in-one-tense
    Hugin1 citation
  99. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-tax-fraud-116-to-304-billion
    Hugin1 citation
  100. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-the-ad-tools-and-the-impersonators
    Hugin1 citation
  101. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-the-elevator-bearings
    Hugin1 citation
  102. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-the-foreign-language-files
    Hugin1 citation
  103. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-the-heart-pump-controller
    Hugin1 citation
  104. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-two-courts-opposite-answers
    Hugin1 citation
  105. hugin.studioHTTP 200
    https://hugin.studio/news/september-27-two-releases-one-tuesday
    Hugin1 citation
  106. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-chatgpt-credit-score-terms
    Hugin1 citation
  107. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-corteva-loyalty-settlement
    Hugin1 citation
  108. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-f150-fuel-tank-recall
    Hugin1 citation
  109. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-gemini-flash-prices-double
    Hugin1 citation
  110. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-home-ventilator-reboot-alert
    Hugin1 citation
  111. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-mercedes-rollaway-two-letters
    Hugin1 citation
  112. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-parking-lot-phone-scam
    Hugin1 citation
  113. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-sprinkler-recall-from-2001
    Hugin1 citation
  114. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-three-ai-models-go-dark
    Hugin1 citation
  115. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-title-i-monitoring-stopped
    Hugin1 citation
  116. hugin.studioHTTP 200
    https://hugin.studio/news/september-28-truck-lease-scheme-two-totals
    Hugin1 citation
  117. hugin.studioHTTP 200
    https://hugin.studio/news/september-8-four-kinds-of-merchant
    Hugin1 citation
  118. hugin.studioHTTP 200
    https://hugin.studio/r/749-8dj-2qp
    Hugin1 citation
  119. learn.microsoft.comHTTP 200
    https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule
    Microsoft2 citations
  120. legacy.sba.govHTTP 200
    https://legacy.sba.gov/article/2026/09/14/sba-announces-suspensions-870000-us-borrowers-tied-39-billion-suspected-pandemic-fraud
    U.S. Small Business Administration1 citation
  121. legacy.sba.govHTTP 200
    https://legacy.sba.gov/article/2026/09/23/sba-referral-leads-irs-investigate-tax-liabilities-related-potentially-100-billion-covid-loan-fraud
    U.S. Small Business Administration1 citation
  122. media.ca11.uscourts.govHTTP 200
    https://media.ca11.uscourts.gov/opinions/pub/files/201913843.enb.pdf
    U.S. Court of Appeals for the Eleventh Circuit1 citation
  123. media.cadc.uscourts.govHTTP 200
    https://media.cadc.uscourts.gov/opinions/docs/2026/09/26-1049-2194984.pdf
    U.S. Court of Appeals for the District of Columbia Circuit1 citation
  124. nmdoj.govHTTP 200
    https://nmdoj.gov/get-help/epstein-zorro-tips/
    New Mexico Department of Justice1 citation
  125. nmdoj.govHTTP 200
    https://nmdoj.gov/press-release/attorney-general-raul-torrez-and-deutsche-bank-announce-joint-efforts-to-fight-human-trafficking/
    New Mexico Department of Justice1 citation
  126. nmdoj.govHTTP 200
    https://nmdoj.gov/press-release/attorney-general-raul-torrez-usdoj-is-hindering-our-criminal-investigation-by-withholding-unredacted-epstein-files/
    New Mexico Department of Justice1 citation
  127. nmdoj.govHTTP 200
    https://nmdoj.gov/press-release/new-mexico-sues-doj-for-blocking-access-to-unredacted-epstein-investigative-files-in-zorro-ranch-criminal-probe/
    New Mexico Department of Justice1 citation
  128. nmdoj.govHTTP 200
    https://nmdoj.gov/press-release/statement-from-new-mexico-department-of-justice-spokesperson-regarding-todays-search-of-the-former-zorro-ranch/
    New Mexico Department of Justice1 citation
  129. nmdoj.govHTTP 200
    https://nmdoj.gov/press-release/statement-from-the-new-mexico-department-of-justice-regarding-zorro-ranch/
    New Mexico Department of Justice1 citation
  130. nmdoj.govHTTP 200
    https://nmdoj.gov/wp-content/uploads/NM-Epstein-Touhy-Cmp_FILED.pdf
    New Mexico Department of Justice, filed in the U.S. District Court for the District of Columbia1 citation
  131. ocrportal.hhs.govHTTP 200
    https://ocrportal.hhs.gov/ocr/breach/breach_report_hip.jsf
    U.S. Department of Health and Human Services Office for Civil Rights1 citation
  132. oecd.aiHTTP 200
    https://oecd.ai/en/dashboards/policy-initiatives/executive-order-14179-removing-barriers-to-american-leadership-in-ai
    OECD.AI Policy Observatory1 citation
  133. ofac.treasury.govHTTP 200
    https://ofac.treasury.gov/sanctions-list-service
    U.S. Department of the Treasury Office of Foreign Assets Control1 citation
  134. oig.hhs.govHTTP 200
    https://oig.hhs.gov/fraud/enforcement/covid-19-fraud-enforcement-task-force-releases-2024-report/
    U.S. Department of Health and Human Services, Office of Inspector General1 citation
  135. oig.hhs.govHTTP 200
    https://oig.hhs.gov/reports/all/2026/medicare-advantage-compliance-audit-of-specific-diagnosis-codes-that-unitedhealthcare-benefits-of-texas-inc-contract-h0609-submitted-to-cms/
    U.S. Department of Health and Human Services, Office of Inspector General1 citation
  136. oig.hhs.govHTTP 200
    https://oig.hhs.gov/reports/all/2026/new-york-made-unallowable-managed-care-capitation-payments-on-behalf-of-incarcerated-medicaid-enrollees/
    U.S. Department of Health and Human Services, Office of Inspector General1 citation
  137. oig.hhs.govHTTP 200
    https://oig.hhs.gov/reports/all/2026/tennessee-claimed-federal-medicaid-reimbursement-for-millions-of-dollars-in-targeted-case-management-services-that-did-not-comply-with-federal-and-state-requirements/
    U.S. Department of Health and Human Services, Office of Inspector General1 citation
  138. oig.justice.govHTTP 200
    https://oig.justice.gov/news/doj-oig-announces-initiation-audit
    U.S. Department of Justice Office of the Inspector General1 citation
  139. oig.justice.govHTTP 200
    https://oig.justice.gov/news/press-release/ppp-loan-recipient-pleaded-guilty-bank-fraud-case-handled-oig-behalf-pandemic
    U.S. Department of Justice, Office of the Inspector General1 citation
  140. oig.justice.govHTTP 200
    https://oig.justice.gov/reports/investigation-and-review-federal-bureau-prisons-custody-care-and-supervision-jeffrey
    U.S. Department of Justice Office of the Inspector General1 citation
  141. oig.ssa.govHTTP 200
    https://oig.ssa.gov/~assets/audits/full/022310.pdf
    Social Security Administration, Office of the Inspector General1 citation
  142. oig.ssa.govHTTP 200
    https://oig.ssa.gov/~assets/audits/full/022515.pdf
    Social Security Administration, Office of the Inspector General1 citation
  143. open.fda.govHTTP 200
    https://open.fda.gov/apis/food/enforcement/
    openFDA1 citation
  144. open.gsa.govHTTP 200
    https://open.gsa.gov/api/entity-api/
    GSA Open Technology1 citation
  145. open.gsa.govHTTP 200
    https://open.gsa.gov/api/exclusions-api/
    U.S. General Services Administration / GSA Open Technology2 citations
  146. openai.comHTTP 200
    https://openai.com/index/a-scorecard-for-the-ai-age/
    OpenAI1 citation
  147. openai.comHTTP 200
    https://openai.com/index/advancing-the-next-era-of-national-science/
    OpenAI1 citation
  148. openai.comHTTP 200
    https://openai.com/index/expanding-ai-access-us-government/
    OpenAI1 citation
  149. openai.comHTTP 200
    https://openai.com/index/gpt-5-6/
    OpenAI1 citation
  150. openai.comHTTP 200
    https://openai.com/index/gpt-6-astra/
    OpenAI1 citation
  151. openai.comHTTP 200
    https://openai.com/index/health-in-chatgpt/
    OpenAI1 citation
  152. openai.comHTTP 200
    https://openai.com/index/how-ai-is-expanding-what-people-do-at-work/
    OpenAI1 citation
  153. openai.comHTTP 200
    https://openai.com/index/hugging-face-model-evaluation-security-incident/
    OpenAI1 citation
  154. openai.comHTTP 200
    https://openai.com/index/introducing-codex/
    OpenAI1 citation
  155. openai.comHTTP 200
    https://openai.com/index/introducing-gpt-5-5/
    OpenAI1 citation
  156. openai.comHTTP 200
    https://openai.com/index/introducing-gpt-6-sol-and-luna/
    OpenAI1 citation
  157. openai.comHTTP 200
    https://openai.com/index/introducing-openai-presence/
    OpenAI1 citation
  158. openai.comHTTP 200
    https://openai.com/index/model-misalignment-reporting-framework/
    OpenAI1 citation
  159. openai.comHTTP 200
    https://openai.com/index/previewing-gpt-5-6-sol/
    OpenAI1 citation
  160. openai.comHTTP 200
    https://openai.com/index/running-codex-safely/
    OpenAI1 citation
  161. openai.comHTTP 200
    https://openai.com/index/safety-overview-gpt-6-astra/
    OpenAI1 citation
  162. openai.comHTTP 200
    https://openai.com/index/unlocking-self-improvement-gpt-red/
    OpenAI1 citation
  163. openai.comHTTP 200
    https://openai.com/index/work-with-codex-from-anywhere/
    OpenAI1 citation
  164. openai.comHTTP 200
    https://openai.com/policies/credit-score-terms/
    OpenAI1 citation
  165. openai.comHTTP 200
    https://openai.com/products/release-notes/
    OpenAI2 citations
  166. openpaymentsdata.cms.govHTTP 200
    https://openpaymentsdata.cms.gov/about/api
    Centers for Medicare & Medicaid Services1 citation
  167. oversight.house.govHTTP 200
    https://oversight.house.gov/release/chairman-comer-announces-markup-of-resolution-to-hold-leon-black-in-contempt-of-congress/
    U.S. House Committee on Oversight and Government Reform1 citation
  168. oversight.house.govHTTP 200
    https://oversight.house.gov/release/chairman-comer-introduces-the-survivors-voice-protection-act/
    U.S. House Committee on Oversight and Government Reform1 citation
  169. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-releases-additional-epstein-estate-documents/
    U.S. House Committee on Oversight and Government Reform1 citation
  170. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-releases-additional-epstein-investigation-transcripts/
    U.S. House Committee on Oversight and Government Reform1 citation
  171. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-releases-epstein-records-provided-by-the-department-of-justice/
    U.S. House Committee on Oversight and Government Reform1 citation
  172. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-releases-kathryn-ruemmler-transcript/
    U.S. House Committee on Oversight and Government Reform1 citation
  173. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-releases-leon-black-and-doug-band-transcripts/
    U.S. House Committee on Oversight and Government Reform1 citation
  174. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-releases-records-provided-by-the-epstein-estate-chairman-comer-provides-statement/
    U.S. House Committee on Oversight and Government Reform1 citation
  175. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-releases-waitt-and-lutnick-transcripts/
    U.S. House Committee on Oversight and Government Reform1 citation
  176. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-republicans-and-democrats-hold-leon-black-in-contempt-for-defying-lawful-subpoenas/
    U.S. House Committee on Oversight and Government Reform1 citation
  177. oversight.house.govHTTP 200
    https://oversight.house.gov/release/oversight-committee-seeks-epstein-maxwell-suspicious-activity-reports-from-treasury-department/
    U.S. House Committee on Oversight and Government Reform1 citation
  178. oversight.house.govHTTP 200
    https://oversight.house.gov/wp-content/uploads/2026/06/Dershowitz-Letter-061226.pdf
    U.S. House Committee on Oversight and Government Reform1 citation
  179. oversightdemocrats.house.govHTTP 200
    https://oversightdemocrats.house.gov/news/press-releases/oversight-democrats-release-third-batch-documents-jeffrey-epstein-estate
    U.S. House Committee on Oversight and Government Reform, Minority1 citation
  180. platform.claude.comHTTP 200
    https://platform.claude.com/docs/en/about-claude/model-deprecations
    Anthropic / Anthropic Docs5 citations
  181. platform.claude.comHTTP 200
    https://platform.claude.com/docs/en/about-claude/pricing
    Anthropic Docs1 citation
  182. pokemongo.comHTTP 200
    https://pokemongo.com/en/news/community-celebrations-go-fest-2026-details-en
    Pokémon GO1 citation
  183. pokemongo.comHTTP 200
    https://pokemongo.com/en/news/go-fest-2026-global-final-details
    Pokémon GO1 citation
  184. pokemongo.comHTTP 200
    https://pokemongo.com/news/road-of-legends-2026
    Pokémon GO1 citation
  185. public-inspection.federalregister.govHTTP 200
    https://public-inspection.federalregister.gov/2026-20143.pdf
    Federal Trade Commission (Federal Register public-inspection copy)1 citation
  186. public-inspection.federalregister.govHTTP 200
    https://public-inspection.federalregister.gov/2026-20321.pdf
    Executive Office of the President (Federal Register public-inspection copy)1 citation
  187. public-inspection.federalregister.govHTTP 200
    https://public-inspection.federalregister.gov/2026-20888.pdf
    U.S. Commodity Futures Trading Commission / Federal Register1 citation
  188. sa15.orgHTTP 200
    https://sa15.org/public-records/
    Office of the State Attorney, 15th Judicial Circuit of Florida1 citation
  189. status.openai.comHTTP 200
    https://status.openai.com/
    OpenAI and Anthropic status pages / OpenAI2 citations
  190. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.cadc.43517/gov.uscourts.cadc.43517.01208890917.0.pdf
    U.S. Department of Justice (filed in the U.S. Court of Appeals for the District of Columbia Circuit)1 citation
  191. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.cadc.43517/gov.uscourts.cadc.43517.01208891196.0.pdf
    U.S. Court of Appeals for the District of Columbia Circuit1 citation
  192. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.cadc.43517/gov.uscourts.cadc.43517.01208892248.0.pdf
    Katie Phang, by counsel (filed in the U.S. Court of Appeals for the District of Columbia Circuit)1 citation
  193. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.cand.465515/gov.uscourts.cand.465515.251.0_2.pdf
    U.S. District Court for the Northern District of California (via CourtListener RECAP)1 citation
  194. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.287475/gov.uscourts.dcd.287475.23.0.pdf
    Democracy Forward Foundation and the U.S. Department of Justice (joint filing, U.S. District Court for the District of Columbia)1 citation
  195. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.15.0_1.pdf
    U.S. District Court for the District of Columbia1 citation
  196. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.23.0.pdf
    U.S. District Court for the District of Columbia1 citation
  197. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.25.0_1.pdf
    U.S. District Court for the District of Columbia1 citation
  198. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.26.0.pdf
    U.S. District Court for the District of Columbia1 citation
  199. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.27.0.pdf
    U.S. District Court for the District of Columbia1 citation
  200. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.28.0.pdf
    U.S. District Court for the District of Columbia1 citation
  201. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.29.0_2.pdf
    U.S. District Court for the District of Columbia1 citation
  202. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.35.0.pdf
    U.S. Department of Justice (filed in the U.S. District Court for the District of Columbia)1 citation
  203. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.37.0.pdf
    U.S. Department of Justice (filed in the U.S. District Court for the District of Columbia)1 citation
  204. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.40.0.pdf
    Katie Phang, by counsel (filed in the U.S. District Court for the District of Columbia)1 citation
  205. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.42.0.pdf
    U.S. District Court for the District of Columbia1 citation
  206. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.43.0.pdf
    U.S. District Court for the District of Columbia1 citation
  207. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.49.0.pdf
    U.S. District Court for the District of Columbia1 citation
  208. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.291779/gov.uscourts.dcd.291779.50.0.pdf
    U.S. Department of Justice (filed in the U.S. District Court for the District of Columbia)1 citation
  209. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.dcd.296175/gov.uscourts.dcd.296175.1.0.pdf
    Leon D. Black, by counsel (filed in the U.S. District Court for the District of Columbia)1 citation
  210. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.flsd.693362/gov.uscourts.flsd.693362.135.0.pdf
    U.S. District Court for the Southern District of Florida1 citation
  211. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.nysd.539612/gov.uscourts.nysd.539612.866.0.pdf
    U.S. District Court for the Southern District of New York1 citation
  212. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.nysd.539612/gov.uscourts.nysd.539612.869.0.pdf
    U.S. District Court for the Southern District of New York1 citation
  213. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.nysd.539612/gov.uscourts.nysd.539612.870.0.pdf
    U.S. District Court for the Southern District of New York1 citation
  214. storage.courtlistener.comHTTP 200
    https://storage.courtlistener.com/recap/gov.uscourts.vaed.607104/gov.uscourts.vaed.607104.37.0.pdf
    U.S. District Court for the Eastern District of Virginia, Alexandria Division (read via CourtListener RECAP)1 citation
  215. support.claude.comHTTP 200
    https://support.claude.com/en/articles/15910845-claude-code-may-august-2026-weekly-limits-promotion
    Anthropic1 citation
  216. thenewstack.ioHTTP 200
    https://thenewstack.io/gpt-5-6-codex-user-surge/
    The New Stack1 citation
  217. usvidoj.comHTTP 200
    https://usvidoj.com/u-s-virgin-islands-attorney-general-settles-sex-trafficking-case-against-estate-of-jeffrey-epstein-and-co-defendants-for-over-105-million/
    U.S. Virgin Islands Department of Justice1 citation
  218. usvidoj.comHTTP 200
    https://usvidoj.com/usvi-doj-achieves-historic-75-million-victim-supporting-settlement-with-jpmorganchase/
    U.S. Virgin Islands Department of Justice1 citation
  219. vault.fbi.govHTTP 200
    https://vault.fbi.gov/jeffrey-epstein
    Federal Bureau of Investigation1 citation
  220. web.archive.orgHTTP 200
    https://web.archive.org/web/20211224194000/https://www.justice.gov/opa/pr/attorney-general-announces-task-force-combat-covid-19-fraud
    U.S. Department of Justice, Office of Public Affairs1 citation
  221. acquisition.govHTTP 200
    https://www.acquisition.gov/far/part-3
    Acquisition.gov1 citation
  222. acquisition.govHTTP 200
    https://www.acquisition.gov/far/part-39
    Acquisition.gov1 citation
  223. anthropic.comHTTP 200
    https://www.anthropic.com/claude-fable-and-mythos-5-1
    Anthropic1 citation
  224. anthropic.comHTTP 200
    https://www.anthropic.com/claude-opus-5-5
    Anthropic1 citation
  225. anthropic.comHTTP 200
    https://www.anthropic.com/news/claude-for-teachers
    Anthropic1 citation
  226. anthropic.comHTTP 200
    https://www.anthropic.com/news/claude-opus-5
    Anthropic1 citation
  227. anthropic.comHTTP 200
    https://www.anthropic.com/news/fable-mythos-access
    Anthropic1 citation
  228. anthropic.comHTTP 200
    https://www.anthropic.com/news/fable-safeguards-jailbreak-framework
    Anthropic1 citation
  229. anthropic.comHTTP 200
    https://www.anthropic.com/news/hard-questions
    Anthropic1 citation
  230. anthropic.comHTTP 200
    https://www.anthropic.com/news/introducing-claude-tag
    Anthropic1 citation
  231. anthropic.comHTTP 200
    https://www.anthropic.com/news/investigating-incidents-cybersecurity-evals
    Anthropic1 citation
  232. anthropic.comHTTP 200
    https://www.anthropic.com/news/redeploying-fable-5
    Anthropic1 citation
  233. anthropic.comHTTP 200
    https://www.anthropic.com/news/reflect-with-claude
    Anthropic1 citation
  234. axios.comHTTP 200
    https://www.axios.com/2026/07/08/openai-gpt-trump-ban-lifted
    Axios1 citation
  235. businessinsider.comHTTP 200
    https://www.businessinsider.com/openai-anthropic-out-freebie-each-other-codex-claude-code-2026-5
    Business Insider1 citation
  236. businessinsider.comHTTP 200
    https://www.businessinsider.com/openai-sol-terra-luna-gpt56-grok-elon-musk-sam-altman-2026-7
    Business Insider1 citation
  237. cftc.govHTTP 200
    https://www.cftc.gov/media/14691/ENF_BrianEarlyAlishaKingreyJudgementOrder091526/download
    U.S. District Court for the Middle District of Florida1 citation
  238. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/8766-23
    U.S. Commodity Futures Trading Commission1 citation
  239. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/8837-23
    U.S. Commodity Futures Trading Commission1 citation
  240. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/9256-26
    U.S. Commodity Futures Trading Commission1 citation
  241. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/9280-26
    U.S. Commodity Futures Trading Commission1 citation
  242. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/9285-26
    U.S. Commodity Futures Trading Commission1 citation
  243. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/9304-26
    U.S. Commodity Futures Trading Commission1 citation
  244. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/9305-26
    U.S. Commodity Futures Trading Commission1 citation
  245. cftc.govHTTP 200
    https://www.cftc.gov/PressRoom/PressReleases/9307-26
    U.S. Commodity Futures Trading Commission1 citation
  246. cnbc.comHTTP 200
    https://www.cnbc.com/2026/07/08/openai-expanding-gpt-5point6-ai-model-release-ending-government-limits.html
    CNBC1 citation
  247. cnbc.comHTTP 200
    https://www.cnbc.com/2026/07/30/open-ai-price-cut-gpt.html
    CNBC1 citation
  248. commerce.senate.govHTTP 200
    https://www.commerce.senate.gov/press/rep/release/wicker-releases-committee-s-faa-investigation-report-2020-12/
    U.S. Senate Committee on Commerce, Science, and Transportation1 citation
  249. congress.govHTTP 200
    https://www.congress.gov/bill/119th-congress/house-bill/4405
    Library of Congress / Congress.gov1 citation
  250. congress.govHTTP 200
    https://www.congress.gov/crs-product/IF12843
    Congressional Research Service (Library of Congress)1 citation
  251. consumerfinance.govHTTP 200
    https://www.consumerfinance.gov/about-us/newsroom/the-cfpb-is-correcting-flaws-to-restore-integrity-and-utility-to-the-consumer-complaint-system/
    Consumer Financial Protection Bureau1 citation
  252. consumerfinance.govHTTP 200
    https://www.consumerfinance.gov/data-research/consumer-complaints/
    Consumer Financial Protection Bureau1 citation
  253. consumerfinance.govHTTP 200
    https://www.consumerfinance.gov/enforcement/actions/
    Consumer Financial Protection Bureau1 citation
  254. cpsc.govHTTP 200
    https://www.cpsc.gov/Newsroom/News-Releases/2026/CPSC-and-Tyco-Fire-Products-LP-Urge-Immediate-Action-on-Recalled-Fire-Sprinklers-that-Can-Fail-in-a-Fire
    U.S. Consumer Product Safety Commission (release 26-800)1 citation
  255. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2026/ABC-Trading-Recalls-Light-Up-Childrens-Toys-Due-to-Risk-of-Serious-Injury-or-Death-from-Battery-Ingestion-Violate-Mandatory-Standard-for-Toys
    U.S. Consumer Product Safety Commission1 citation
  256. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2026/JKMAX-Recalls-Heated-Blankets-and-Heating-Pads-Due-to-Fire-and-Burn-Hazards
    U.S. Consumer Product Safety Commission1 citation
  257. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2026/NEWDERY-Power-Banks-Recalled-Due-to-Fire-and-Burn-Hazards-Risk-of-Serious-Injury-Sold-on-Amazon
    U.S. Consumer Product Safety Commission1 citation
  258. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2026/Sauna360-Expands-Recall-of-Tylo-Halmstad-and-Kiruna-Hybrid-Saunas-Due-to-Fall-Hazard-New-Remedy-Provided
    U.S. Consumer Product Safety Commission1 citation
  259. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2026/The-Blue-Cactus-Company-Reclining-Chair-Battery-Packs-Recalled-Due-to-Fire-and-Burn-Hazards-Sold-on-Amazon
    U.S. Consumer Product Safety Commission1 citation
  260. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2026/Yuyitop-Recalls-Aitjunz-8-Drawer-Dressers-Due-to-Risk-of-Serious-Injury-or-Death-from-Tip-Over-and-Entrapment-Hazards-Violate-Mandatory-Standard-for-Clothing-Storage-Units
    U.S. Consumer Product Safety Commission1 citation
  261. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2026/ZCK01-Recalls-Kesyup-Mattresses-Due-to-Risk-of-Serious-Injury-or-Death-from-Fire-Hazard-Violate-Mandatory-Standard-for-Mattress-Flammability
    U.S. Consumer Product Safety Commission1 citation
  262. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/2027/3M-Company-Recalls-ScotchTM-Thermal-Laminators-Due-to-Risk-of-Serious-Injury-or-Death-from-Fire-Hazard
    U.S. Consumer Product Safety Commission1 citation
  263. cpsc.govHTTP 200
    https://www.cpsc.gov/Recalls/CPSC-Recalls-Application-Program-Interface-API-Information
    U.S. Consumer Product Safety Commission1 citation
  264. dfs.ny.govHTTP 200
    https://www.dfs.ny.gov/reports_and_publications/press_releases/pr202007071
    New York State Department of Financial Services1 citation
  265. engadget.comHTTP 200
    https://www.engadget.com/2210308/openai-rolls-out-gpt5-6-july-9/
    Engadget1 citation
  266. fac.govHTTP 200
    https://www.fac.gov/api/
    Federal Audit Clearinghouse1 citation
  267. fda.govHTTP 200
    https://www.fda.gov/medical-devices/medical-device-recalls-and-early-alerts/early-alert-ventilator-issue-react-health
    U.S. Food and Drug Administration, Center for Devices and Radiological Health1 citation
  268. fda.govHTTP 200
    https://www.fda.gov/medical-devices/medical-device-recalls-and-early-alerts/heart-pump-controller-recall-abiomed-removes-automated-impella-controllers
    U.S. Food and Drug Administration, Center for Devices and Radiological Health1 citation
  269. fda.govHTTP 200
    https://www.fda.gov/safety/recalls-market-withdrawals-safety-alerts
    U.S. Food and Drug Administration1 citation
  270. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/full_text/text/2026/10/09/2026-20726.txt
    U.S. Food and Drug Administration / Federal Register1 citation
  271. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/full_text/text/2026/10/19/2026-21320.txt
    U.S. Office of Personnel Management (Federal Register)1 citation
  272. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/full_text/text/2026/10/19/2026-21348.txt
    U.S. Consumer Product Safety Commission (Federal Register)1 citation
  273. federalregister.govHTTP 200
    https://www.federalregister.gov/public-inspection/raw_text/202/620/296.txt
    U.S. Consumer Product Safety Commission (Federal Register public-inspection copy)1 citation
  274. federalregister.govHTTP 200
    https://www.federalregister.gov/public-inspection/raw_text/202/621/320.txt
    U.S. Office of Personnel Management (Federal Register)1 citation
  275. federalregister.govHTTP 200
    https://www.federalregister.gov/public-inspection/raw_text/202/621/348.txt
    U.S. Consumer Product Safety Commission (Federal Register)1 citation
  276. federalregister.govHTTP 200
    https://www.federalregister.gov/public-inspection/raw_text/202/621/420.txt
    U.S. Department of Health and Human Services, Centers for Medicare & Medicaid Services (Federal Register)1 citation
  277. flsenate.govHTTP 200
    https://www.flsenate.gov/Session/Bill/2024/117
    The Florida Senate1 citation
  278. foxnews.comHTTP 200
    https://www.foxnews.com/science/trump-puts-brakes-openais-newest-ai-model
    Fox News1 citation
  279. ftc.govHTTP 200
    https://www.ftc.gov/enforcement/refunds/cleo-ai-refunds
    Federal Trade Commission1 citation
  280. ftc.govHTTP 200
    https://www.ftc.gov/legal-library/browse/cases-proceedings/humboldt-merchant-services
    Federal Trade Commission2 citations
  281. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2024/09/ftc-announces-crackdown-deceptive-ai-claims-schemes
    Federal Trade Commission1 citation
  282. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2024/12/ftc-order-requires-online-retailer-goat-pay-more-2-million-consumers-mail-order-rule-violations
    Federal Trade Commission1 citation
  283. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2025/03/cash-advance-company-cleo-ai-agrees-pay-17-million-result-ftc-lawsuit-charging-it-deceives-consumers
    Federal Trade Commission1 citation
  284. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2025/12/ftc-reopens-sets-aside-rytr-final-order-response-trump-administrations-ai-action-plan
    Federal Trade Commission1 citation
  285. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/02/ftc-reminds-data-brokers-their-obligations-comply-padfaa
    Federal Trade Commission1 citation
  286. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/05/ftc-ban-kochava-subsidiary-selling-sensitive-location-data-settle-charges-they-sold-location-data
    Federal Trade Commission1 citation
  287. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/07/ftc-seeks-public-comment-policy-statement-addressing-ai-accuracy
    Federal Trade Commission2 citations
  288. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/08/ftc-finalizes-orders-cox-media-group-two-other-firms-settling-charges-they-deceived-customers-about
    Federal Trade Commission1 citation
  289. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/09/fleetcor-agrees-pay-100-million-resolve-administrative-action-after-federal-court-finds-it-violated
    Federal Trade Commission1 citation
  290. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/09/ftc-announces-additional-payments-consumers-stemming-ftcs-amazon-prime-settlement
    Federal Trade Commission1 citation
  291. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/09/ftc-seeks-public-comment-whether-update-rule-impersonation-government-businesses-address-platforms
    Federal Trade Commission1 citation
  292. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/09/ftc-states-win-protections-lower-pesticide-prices-american-farmers-antitrust-case-against-corteva
    Federal Trade Commission1 citation
  293. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/09/ftc-takes-historic-action-against-multilevel-marketing-operator-amway-unfair-deceptive-business
    Federal Trade Commission1 citation
  294. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/10/ftc-issues-letters-warning-hospitals-against-deceptive-pricing-practices
    Federal Trade Commission1 citation
  295. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/10/ftc-issues-redress-payments-consumers-impacted-goats-deceptive-shipping-refund-policies
    Federal Trade Commission1 citation
  296. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/10/ftc-returns-more-158-million-consumers-misled-cash-advance-app-company-cleo-ai
    Federal Trade Commission1 citation
  297. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/10/ftc-secures-settlement-protects-small-businesses-illegal-price-discrimination
    Federal Trade Commission1 citation
  298. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/10/ftc-states-sue-lenscom-misrepresenting-price-contact-lenses-search-ads-its-website
    Federal Trade Commission1 citation
  299. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/10/ftc-usda-seek-public-comment-agricultural-equipment-manufacturing-distribution-market-practices
    Federal Trade Commission1 citation
  300. ftc.govHTTP 200
    https://www.ftc.gov/news-events/news/press-releases/2026/10/premier-martial-arts-franchisor-its-former-franchise-sales-organization-settle-ftc-charges-companies
    Federal Trade Commission1 citation
  301. ftc.govHTTP 200
    https://www.ftc.gov/news-events/topics/protecting-consumer-privacy-security/privacy-security-enforcement
    Federal Trade Commission1 citation
  302. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/2026-older-adults-report-10192026.pdf
    Federal Trade Commission1 citation
  303. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/2123050amazonprimeredressfundorder.pdf
    U.S. District Court for the Western District of Washington (published by the Federal Trade Commission)1 citation
  304. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/cleo_order_-_executed_-_for_press_release.pdf
    Federal Trade Commission1 citation
  305. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/Hospital-Letter-Template.pdf
    Federal Trade Commission1 citation
  306. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/Humboldt-StipulatedOrder_0.pdf
    U.S. District Court for the Eastern District of Michigan (published by the Federal Trade Commission)1 citation
  307. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/Kochava-Order.pdf
    U.S. District Court for the District of Idaho, posted by the Federal Trade Commission1 citation
  308. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/Lens.com-Complaint.pdf
    Federal Trade Commission (filed in the U.S. District Court for the District of Nevada)1 citation
  309. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/RFI-AgEquipment.pdf
    Federal Trade Commission and U.S. Department of Agriculture1 citation
  310. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/SGWS-ProposedStipulatedConsentDecreeandOrder.pdf
    Federal Trade Commission (filed in the U.S. District Court for the Central District of California)1 citation
  311. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/StipulatedOrder-FFL.pdf
    Federal Trade Commission1 citation
  312. ftc.govHTTP 200
    https://www.ftc.gov/system/files/ftc_gov/pdf/StipulatedOrder-PFG.pdf
    Federal Trade Commission1 citation
  313. gao.govHTTP 200
    https://www.gao.gov/blog/186-billion-was-lost-improper-payments-last-year-how-can-we-prevent-them-future
    U.S. Government Accountability Office1 citation
  314. gao.govHTTP 200
    https://www.gao.gov/products/gao-21-519sp
    Government Accountability Office1 citation
  315. gao.govHTTP 200
    https://www.gao.gov/products/gao-22-105715
    U.S. Government Accountability Office1 citation
  316. gao.govHTTP 200
    https://www.gao.gov/products/gao-23-106285
    U.S. Government Accountability Office1 citation
  317. gao.govHTTP 200
    https://www.gao.gov/products/gao-23-106586
    U.S. Government Accountability Office1 citation
  318. gao.govHTTP 200
    https://www.gao.gov/products/gao-23-106696
    U.S. Government Accountability Office1 citation
  319. gao.govHTTP 200
    https://www.gao.gov/products/gao-24-105833
    U.S. Government Accountability Office1 citation
  320. gao.govHTTP 200
    https://www.gao.gov/products/gao-24-107332
    Government Accountability Office1 citation
  321. gao.govHTTP 200
    https://www.gao.gov/products/gao-24-107660
    U.S. Government Accountability Office1 citation
  322. gao.govHTTP 200
    https://www.gao.gov/products/gao-25-107653
    Government Accountability Office1 citation
  323. gao.govHTTP 200
    https://www.gao.gov/products/gao-25-107743
    U.S. Government Accountability Office1 citation
  324. gao.govHTTP 200
    https://www.gao.gov/products/gao-25-107746
    U.S. Government Accountability Office1 citation
  325. gao.govHTTP 200
    https://www.gao.gov/products/gao-25-107753
    U.S. Government Accountability Office1 citation
  326. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-107466
    U.S. Government Accountability Office1 citation
  327. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-107774
    U.S. Government Accountability Office1 citation
  328. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-107810
    U.S. Government Accountability Office1 citation
  329. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-107920
    U.S. Government Accountability Office1 citation
  330. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108017
    U.S. Government Accountability Office2 citations
  331. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108174
    U.S. Government Accountability Office1 citation
  332. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108477
    U.S. Government Accountability Office1 citation
  333. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108530
    U.S. Government Accountability Office1 citation
  334. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108596
    U.S. Government Accountability Office1 citation
  335. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108663
    U.S. Government Accountability Office1 citation
  336. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108694
    U.S. Government Accountability Office1 citation
  337. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-108850
    U.S. Government Accountability Office1 citation
  338. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-109096
    U.S. Government Accountability Office1 citation
  339. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-109097
    U.S. Government Accountability Office1 citation
  340. gao.govHTTP 200
    https://www.gao.gov/products/gao-26-109100
    U.S. Government Accountability Office2 citations
  341. gao.govHTTP 200
    https://www.gao.gov/products/gao-27-108176
    U.S. Government Accountability Office1 citation
  342. gao.govHTTP 200
    https://www.gao.gov/products/gao-27-108853
    U.S. Government Accountability Office1 citation
  343. gao.govHTTP 200
    https://www.gao.gov/rss/reports.xml
    U.S. Government Accountability Office1 citation
  344. govinfo.govHTTP 200
    https://www.govinfo.gov/app/details/BILLS-118s3312rs
    U.S. Congress (GovInfo BILLS)1 citation
  345. govinfo.govHTTP 200
    https://www.govinfo.gov/app/details/GOVPUB-C13-ef6882c6bd970bc733de394f469ea3f3
    U.S. Government Publishing Office (GovInfo)1 citation
  346. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/BILLS-119hr10389ih/html/BILLS-119hr10389ih.htm
    U.S. Government Publishing Office (GovInfo)1 citation
  347. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/BILLS-119hr7008eh/html/BILLS-119hr7008eh.htm
    U.S. Government Publishing Office (GovInfo)1 citation
  348. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/BILLS-119hr7008pcs/html/BILLS-119hr7008pcs.htm
    U.S. Government Publishing Office (GovInfo)1 citation
  349. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/BILLS-119hr9694ih/html/BILLS-119hr9694ih.htm
    U.S. Government Publishing Office (GovInfo)1 citation
  350. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/CREC-2026-07-22/html/CREC-2026-07-22-pt1-PgH5157.htm
    Congressional Record (U.S. Government Publishing Office)1 citation
  351. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/CREC-2026-09-16/html/CREC-2026-09-16-pt1-PgH5931.htm
    Congressional Record (U.S. Government Publishing Office)1 citation
  352. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2019-03-18/pdf/2019-05067.pdf
    Federal Aviation Administration / U.S. Government Publishing Office1 citation
  353. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2020-11-20/pdf/2020-25844.pdf
    Federal Aviation Administration / U.S. Government Publishing Office1 citation
  354. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2023-11-01/pdf/2023-24283.pdf
    The White House (GovInfo Compilation of Presidential Documents)1 citation
  355. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2024-10-03/pdf/2024-22767.pdf
    Federal Trade Commission / U.S. Government Publishing Office1 citation
  356. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2025-01-28/pdf/2025-01901.pdf
    The White House / U.S. Government Publishing Office (Federal Register 90 FR 8237)1 citation
  357. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2025-01-31/pdf/2025-02172.pdf
    The White House (GovInfo Compilation of Presidential Documents)1 citation
  358. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-01-08/pdf/2026-00206.pdf
    National Institute of Standards and Technology / U.S. Government Publishing Office1 citation
  359. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-08-27/pdf/2026-17533.pdf
    U.S. Department of Justice (Federal Register)1 citation
  360. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-09-21/pdf/2026-19255.pdf
    Federal Aviation Administration (Federal Register)1 citation
  361. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-10-02/pdf/2026-20319.pdf
    Executive Office of the President (Federal Register)2 citations
  362. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-10-02/pdf/2026-20321.pdf
    Executive Office of the President (Federal Register)1 citation
  363. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20720.htm
    U.S. Food and Drug Administration / Government Publishing Office1 citation
  364. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20721.htm
    U.S. Food and Drug Administration / Government Publishing Office1 citation
  365. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20727.htm
    U.S. Food and Drug Administration / Government Publishing Office1 citation
  366. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/PLAW-112publ105/pdf/PLAW-112publ105.pdf
    GovInfo / U.S. Government Publishing Office1 citation
  367. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/PLAW-116publ136/html/PLAW-116publ136.htm
    U.S. Government Publishing Office (GovInfo)1 citation
  368. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/PLAW-117publ165/pdf/PLAW-117publ165.pdf
    U.S. Government Publishing Office (GovInfo)1 citation
  369. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/PLAW-117publ166/pdf/PLAW-117publ166.pdf
    U.S. Government Publishing Office (GovInfo)1 citation
  370. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/PLAW-119publ21/html/PLAW-119publ21.htm
    U.S. Government Publishing Office (GovInfo)1 citation
  371. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/PLAW-119publ38/pdf/PLAW-119publ38.pdf
    GovInfo / U.S. Government Publishing Office1 citation
  372. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/USCODE-2024-title15/html/USCODE-2024-title15-chap119-sec9401.htm
    U.S. Government Publishing Office (GovInfo)1 citation
  373. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/USCOURTS-ca2-22-01426/pdf/USCOURTS-ca2-22-01426-0.pdf
    U.S. Court of Appeals for the Second Circuit1 citation
  374. gsa.govHTTP 200
    https://www.gsa.gov/about-gsa/newsroom/news-releases/gsa-announces-coras-partnership-through-onegov-07282026
    U.S. General Services Administration1 citation
  375. gsa.govHTTP 200
    https://www.gsa.gov/about-gsa/newsroom/news-releases/gsa-expands-onegov-ai-offerings-with-discounted-openais-chatgpt-09102026
    U.S. General Services Administration1 citation
  376. gsa.govHTTP 200
    https://www.gsa.gov/about-gsa/newsroom/news-releases/gsa-hhs-uncover-12-billion-in-suspected-covidrelated-contract-fraud-09242026
    U.S. General Services Administration1 citation
  377. gsa.govHTTP 200
    https://www.gsa.gov/about-gsa/newsroom/news-releases/gsa-issues-statement-on-anthropic-preliminary-injunction-04032026
    U.S. General Services Administration1 citation
  378. gsa.govHTTP 200
    https://www.gsa.gov/about-gsa/newsroom/news-releases/gsa-stands-with-president-trump-on-national-security-ai-directive-02272026
    U.S. General Services Administration1 citation
  379. justice.govHTTP 200
    https://www.justice.gov/civil/civil-division-press-room
    U.S. Department of Justice, Civil Division1 citation
  380. justice.govHTTP 200
    https://www.justice.gov/criminal/case/united-states-v-binance-holdings-limited-dba-binancecom
    U.S. Department of Justice, Criminal Division1 citation
  381. justice.govHTTP 200
    https://www.justice.gov/criminal/criminal-fraud/case/united-states-v-boeing-company
    U.S. Department of Justice, Criminal Division (Fraud Section)1 citation
  382. justice.govHTTP 200
    https://www.justice.gov/criminal/media/1454141/dl?inline
    United States Court of Appeals for the Fifth Circuit (document hosted by the DOJ Criminal Division)1 citation
  383. justice.govHTTP 200
    https://www.justice.gov/crt/media/1466881/dl?inline=
    U.S. Department of Justice1 citation
  384. justice.govHTTP 200
    https://www.justice.gov/epstein/doj-disclosures
    U.S. Department of Justice1 citation
  385. justice.govHTTP 200
    https://www.justice.gov/epstein/doj-disclosures/court-records-government-united-states-virgin-islands-v-jpmorgan-chase-bank-na-no-122-cv-10904-sdny-2022
    U.S. Department of Justice1 citation
  386. justice.govHTTP 200
    https://www.justice.gov/epstein/doj-disclosures/court-records-united-states-v-noel-no-119-cr-00830-sdny-2019
    U.S. Department of Justice1 citation
  387. justice.govHTTP 200
    https://www.justice.gov/media/1426281/dl?inline=
    U.S. Department of Justice1 citation
  388. justice.govHTTP 200
    https://www.justice.gov/oip/democracy-forward-found-v-doj-no-25-2597-2025-wl-3268245-ddc-nov-24-2025-chutkan-j
    U.S. Department of Justice Office of Information Policy1 citation
  389. justice.govHTTP 200
    https://www.justice.gov/opa/media/1434851/dl?inline=
    U.S. Department of Justice1 citation
  390. justice.govHTTP 200
    https://www.justice.gov/opa/media/1434856/dl?inline=
    U.S. Department of Justice1 citation
  391. justice.govHTTP 200
    https://www.justice.gov/opa/pr/alibaba-group-and-aus-merchant-services-agree-pay-600-million-resolve-allegations-they
    U.S. Department of Justice1 citation
  392. justice.govHTTP 200
    https://www.justice.gov/opa/pr/dallas-seafood-business-fined-250000-falsifying-country-origin-salmon
    U.S. Department of Justice1 citation
  393. justice.govHTTP 200
    https://www.justice.gov/opa/pr/department-justice-again-wins-substantial-relief-against-google
    U.S. Department of Justice, Office of Public Affairs1 citation
  394. justice.govHTTP 200
    https://www.justice.gov/opa/pr/department-justice-announces-launch-national-fraud-detection-center-combat-fraud-against
    U.S. Department of Justice, Office of Public Affairs2 citations
  395. justice.govHTTP 200
    https://www.justice.gov/opa/pr/department-justice-announces-results-law-enforcement-and-private-industry-joint-disruption
    U.S. Department of Justice1 citation
  396. justice.govHTTP 200
    https://www.justice.gov/opa/pr/department-justice-publishes-35-million-responsive-pages-compliance-epstein-files
    U.S. Department of Justice Office of Public Affairs1 citation
  397. justice.govHTTP 200
    https://www.justice.gov/opa/pr/doj-revises-justice-manual-strengthen-false-claims-act-enforcement
    U.S. Department of Justice, Office of Public Affairs1 citation
  398. justice.govHTTP 200
    https://www.justice.gov/opa/pr/dojs-fraud-division-sba-and-sba-oig-target-245m-covid-loan-fraud-enforcement-activity-state
    U.S. Department of Justice, Office of Public Affairs (National Fraud Enforcement Division)1 citation
  399. justice.govHTTP 200
    https://www.justice.gov/opa/pr/eyepoint-pharmaceuticals-pay-46-million-resolve-false-claims-act-allegations
    U.S. Department of Justice1 citation
  400. justice.govHTTP 200
    https://www.justice.gov/opa/pr/former-census-bureau-program-manager-sentenced-prison-bribery-and-procurement-fraud
    U.S. Department of Justice1 citation
  401. justice.govHTTP 200
    https://www.justice.gov/opa/pr/former-federal-employee-pleads-guilty-defrauding-federal-government-approximately-194
    U.S. Department of Justice, Office of Public Affairs1 citation
  402. justice.govHTTP 200
    https://www.justice.gov/opa/pr/four-men-plead-guilty-2m-minnesota-medicaid-fraud
    U.S. Department of Justice1 citation
  403. justice.govHTTP 200
    https://www.justice.gov/opa/pr/justice-department-files-complaint-stop-nevada-firm-manufacturing-and-selling-adulterated
    U.S. Department of Justice, Office of Public Affairs1 citation
  404. justice.govHTTP 200
    https://www.justice.gov/opa/pr/justice-department-settles-california-towing-company-illegally-auctioning-servicemembers
    U.S. Department of Justice1 citation
  405. justice.govHTTP 200
    https://www.justice.gov/opa/pr/labcorp-agrees-pay-145m-resolve-false-claims-act-allegations
    U.S. Department of Justice1 citation
  406. justice.govHTTP 200
    https://www.justice.gov/opa/pr/man-serving-federal-prison-sentence-charged-theft-forfeited-cryptocurrency
    U.S. Department of Justice, Office of Public Affairs1 citation
  407. justice.govHTTP 200
    https://www.justice.gov/opa/pr/medical-supply-company-owner-sentenced-14-years-prison-30m-medicare-tricare-and-champva
    U.S. Department of Justice1 citation
  408. justice.govHTTP 200
    https://www.justice.gov/opa/pr/medicare-advantage-provider-complete-health-pay-14100000-settle-false-claims-act-suit
    U.S. Department of Justice, Office of Public Affairs1 citation
  409. justice.govHTTP 200
    https://www.justice.gov/opa/pr/nevada-doctor-charged-95m-wound-care-fraud-medicare
    U.S. Department of Justice, Office of Public Affairs1 citation
  410. justice.govHTTP 200
    https://www.justice.gov/opa/pr/redi-bag-usa-and-ceo-agree-pay-73m-settle-false-claims-act-allegations-relating-evaded
    U.S. Department of Justice1 citation
  411. justice.govHTTP 200
    https://www.justice.gov/opa/pr/texas-mental-health-clinic-owner-convicted-26m-scheme-defraud-military-health-benefits
    U.S. Department of Justice, Office of Public Affairs (release 26-2005)1 citation
  412. justice.govHTTP 200
    https://www.justice.gov/opa/pr/trade-fraud-task-force-surpasses-1-billion-recoveries-and-charged-losses-less-one-year
    U.S. Department of Justice1 citation
  413. justice.govHTTP 200
    https://www.justice.gov/opa/pr/two-additional-ophthalmology-practices-agree-pay-23m-resolve-allegations-fraudulent-claims
    U.S. Department of Justice, Office of Public Affairs1 citation
  414. justice.govHTTP 200
    https://www.justice.gov/opa/pr/two-key-members-chinese-money-laundering-network-charged-laundering-43-million-investment
    U.S. Department of Justice, Office of Public Affairs1 citation
  415. justice.govHTTP 200
    https://www.justice.gov/opa/pr/united-states-files-civil-forfeiture-complaint-against-225m-funds-involved-cryptocurrency
    U.S. Department of Justice, Office of Public Affairs1 citation
  416. justice.govHTTP 200
    https://www.justice.gov/opr/page/file/1336471/dl
    U.S. Department of Justice Office of Professional Responsibility1 citation
  417. justice.govHTTP 200
    https://www.justice.gov/pardon/clemency-grants-president-donald-j-trump-2025-present
    U.S. Department of Justice, Office of the Pardon Attorney1 citation
  418. justice.govHTTP 200
    https://www.justice.gov/pardon/media/1416576/dl?inline
    U.S. Department of Justice, Office of the Pardon Attorney1 citation
  419. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/united-states-v-ghislaine-maxwell
    U.S. Attorney's Office, Southern District of New York1 citation
  420. nist.govHTTP 200
    https://www.nist.gov/itl/ai-risk-management-framework
    National Institute of Standards and Technology2 citations
  421. nist.govHTTP 200
    https://www.nist.gov/news-events/news/2026/09/caisis-assessment-zais-glm-53-cyber-capabilities
    National Institute of Standards and Technology / Center for AI Standards and Innovation1 citation
  422. nist.govHTTP 200
    https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence
    National Institute of Standards and Technology2 citations
  423. ntsb.govHTTP 200
    https://www.ntsb.gov/investigations/AccidentReports/Reports/AIR2504.pdf
    National Transportation Safety Board1 citation
  424. ntsb.govHTTP 200
    https://www.ntsb.gov/investigations/Pages/DCA24MA063.aspx
    National Transportation Safety Board1 citation
  425. ntsb.govHTTP 200
    https://www.ntsb.gov/news/press-releases/Pages/NR20250624.aspx
    National Transportation Safety Board1 citation
  426. nysd.uscourts.govHTTP 200
    https://www.nysd.uscourts.gov/sites/default/files/2026-01/Maxwell%2020cr330%20-%20Opinion%20%26%20Order%201.21.26.pdf
    U.S. District Court, Southern District of New York1 citation
  427. oig.dol.govHTTP 200
    https://www.oig.dol.gov/OIG_Pandemic_Response_Portal.htm
    U.S. Department of Labor, Office of Inspector General1 citation
  428. oig.dot.govHTTP 200
    https://www.oig.dot.gov/library-item/38302
    U.S. Department of Transportation, Office of Inspector General1 citation
  429. oig.dot.govHTTP 200
    https://www.oig.dot.gov/library-item/39461
    U.S. Department of Transportation, Office of Inspector General1 citation
  430. oig.dot.govHTTP 200
    https://www.oig.dot.gov/library-item/46466
    U.S. Department of Transportation, Office of Inspector General1 citation
  431. oig.dot.govHTTP 200
    https://www.oig.dot.gov/library-item/47267
    U.S. Department of Transportation, Office of Inspector General1 citation
  432. oversight.govHTTP 200
    https://www.oversight.gov/sites/default/files/documents/reports/2026-09/03-26-001-10-105.pdf
    U.S. Department of Labor, Office of Inspector General1 citation
  433. oversight.govHTTP 200
    https://www.oversight.gov/sites/default/files/documents/reports/2026-09/2026208059fr.pdf
    Treasury Inspector General for Tax Administration1 citation
  434. oversight.govHTTP 200
    https://www.oversight.gov/sites/default/files/documents/reports/2026-09/25-139-R26.pdf
    U.S. Postal Service Office of Inspector General1 citation
  435. oversight.govHTTP 200
    https://www.oversight.gov/sites/default/files/documents/reports/2026-09/26-101.pdf
    U.S. Department of Justice, Office of the Inspector General1 citation
  436. pandemicoversight.govHTTP 200
    https://www.pandemicoversight.gov/
    Pandemic Response Accountability Committee1 citation
  437. pandemicoversight.govHTTP 200
    https://www.pandemicoversight.gov/data-interactive-tools
    Pandemic Response Accountability Committee1 citation
  438. pandemicoversight.govHTTP 200
    https://www.pandemicoversight.gov/news/articles/prac-joins-national-fraud-detection-center-to-strengthen-governmentwide-antifraud-efforts
    Pandemic Response Accountability Committee1 citation
  439. pandemicoversight.govHTTP 200
    https://www.pandemicoversight.gov/oversight/semiannual-reports-to-congress/april-2025-september-2025
    Pandemic Response Accountability Committee1 citation
  440. pandemicoversight.govHTTP 200
    https://www.pandemicoversight.gov/oversight/semiannual-reports-to-congress/october-2025-march-2026
    Pandemic Response Accountability Committee1 citation
  441. pbs.orgHTTP 200
    https://www.pbs.org/newshour/nation/286-million-in-stolen-pandemic-loans-recovered-according-to-u-s-secret-service
    PBS NewsHour1 citation
  442. pymnts.comHTTP 200
    https://www.pymnts.com/news/artificial-intelligence/2026/openai-readies-gpt-5-6-launch-as-white-house-lifts-restriction-request/
    PYMNTS1 citation
  443. recalls.govHTTP 200
    https://www.recalls.gov/
    Recalls.gov1 citation
  444. sec.govHTTP 200
    https://www.sec.gov/Archives/edgar/data/1058623/000110465926116470/tm2625433d5_8k.htm
    Cumulus Media Inc. (via SEC EDGAR)1 citation
  445. sec.govHTTP 200
    https://www.sec.gov/Archives/edgar/data/1058623/000110465926116470/tm2625433d5_ex99-1.htm
    Cumulus Media Inc. (via SEC EDGAR)1 citation
  446. sec.govHTTP 200
    https://www.sec.gov/enforcement-litigation/litigation-releases
    U.S. Securities and Exchange Commission2 citations
  447. sec.govHTTP 200
    https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26570
    U.S. Securities and Exchange Commission1 citation
  448. sec.govHTTP 200
    https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26598
    U.S. Securities and Exchange Commission1 citation
  449. sec.govHTTP 200
    https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26599
    U.S. Securities and Exchange Commission1 citation
  450. sec.govHTTP 200
    https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26608
    U.S. Securities and Exchange Commission1 citation
  451. sec.govHTTP 200
    https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26621
    U.S. Securities and Exchange Commission1 citation
  452. sec.govHTTP 200
    https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26648
    U.S. Securities and Exchange Commission1 citation
  453. sec.govHTTP 200
    https://www.sec.gov/files/company_tickers.json
    U.S. Securities and Exchange Commission1 citation
  454. sec.govHTTP 200
    https://www.sec.gov/files/litigation/complaints/2026/comp-pr2026-98.pdf
    U.S. Securities and Exchange Commission (filed in the U.S. District Court for the Southern District of New York)1 citation
  455. sec.govHTTP 200
    https://www.sec.gov/files/rules/proposed/2026/ia-7023.pdf
    U.S. Securities and Exchange Commission1 citation
  456. sec.govHTTP 200
    https://www.sec.gov/newsroom/press-releases/2023-102
    U.S. Securities and Exchange Commission1 citation
  457. sec.govHTTP 200
    https://www.sec.gov/newsroom/press-releases/2024-73
    U.S. Securities and Exchange Commission1 citation
  458. sec.govHTTP 200
    https://www.sec.gov/newsroom/press-releases/2025-47
    U.S. Securities and Exchange Commission1 citation
  459. sec.govHTTP 200
    https://www.sec.gov/newsroom/press-releases/2026-100-sec-proposal-would-address-how-investment-advisers-funds-can-custody-crypto-assets-under-federal
    U.S. Securities and Exchange Commission1 citation
  460. sec.govHTTP 200
    https://www.sec.gov/newsroom/press-releases/2026-63-sec-forms-new-retail-fraud-working-group
    U.S. Securities and Exchange Commission2 citations
  461. sec.govHTTP 200
    https://www.sec.gov/newsroom/press-releases/2026-76-sec-proposes-new-regulation-crypto-assets
    U.S. Securities and Exchange Commission1 citation
  462. sec.govHTTP 200
    https://www.sec.gov/newsroom/press-releases/2026-98-sec-charges-meyer-global-management-its-ceo-defrauding-retail-investors-private-funds-held-interests
    U.S. Securities and Exchange Commission1 citation
  463. sec.govHTTP 200
    https://www.sec.gov/search-filings/edgar-application-programming-interfaces
    U.S. Securities and Exchange Commission1 citation
  464. secretservice.govHTTP 200
    https://www.secretservice.gov/newsroom/releases/2022/08/us-secret-service-returns-286m-fraudulently-obtained-funds-small-business
    U.S. Secret Service1 citation
  465. securityweek.comHTTP 200
    https://www.securityweek.com/after-openai-disclosure-anthropic-finds-its-own-models-hacked-3-organizations/
    SecurityWeek1 citation
  466. supremecourt.govHTTP 200
    https://www.supremecourt.gov/search.aspx?filename=/docket/docketfiles/html/public/24-1073.html
    Supreme Court of the United States1 citation
  467. supremecourt.govHTTP 200
    https://www.supremecourt.gov/search.aspx?filename=/docket/docketfiles/html/public/26-349.html
    Supreme Court of the United States1 citation
  468. whitehouse.govHTTP 200
    https://www.whitehouse.gov/wp-content/uploads/2024/10/M-24-18-AI-Acquisition-Memorandum.pdf
    Office of Management and Budget1 citation
  469. whitehouse.govHTTP 200
    https://www.whitehouse.gov/wp-content/uploads/2025/02/M-25-21-Accelerating-Federal-Use-of-AI-through-Innovation-Governance-and-Public-Trust.pdf
    Office of Management and Budget1 citation
  470. whitehouse.govHTTP 200
    https://www.whitehouse.gov/wp-content/uploads/2025/02/M-25-22-Driving-Efficient-Acquisition-of-Artificial-Intelligence-in-Government.pdf
    Office of Management and Budget1 citation
  471. whitehouse.govHTTP 200
    https://www.whitehouse.gov/wp-content/uploads/2025/07/Americas-AI-Action-Plan.pdf
    The White House2 citations
  472. x.comHTTP 200
    https://x.com/ClaudeDevs/status/2054639777685934564
    Anthropic / ClaudeDevs1 citation
  473. x.comHTTP 200
    https://x.com/ClaudeDevs/status/2068122937308426676
    Anthropic / ClaudeDevs1 citation
  474. x.comHTTP 200
    https://x.com/ClaudeDevs/status/2078511173759324328
    Anthropic / ClaudeDevs1 citation
  475. x.comHTTP 200
    https://x.com/OpenAI/status/2074704958419792299
    OpenAI1 citation
  476. x.comHTTP 200
    https://x.com/thsottiaux/status/2076365965915467978
    Tibo Sottiaux (OpenAI), via X1 citation
  477. x.comHTTP 200
    https://x.com/thsottiaux/status/2082317452755751098
    Tibo Sottiaux (OpenAI), via X1 citation
  478. x.comHTTP 200
    https://x.com/thsottiaux/status/2082737638583501152
    Tibo Sottiaux (OpenAI), via X1 citation

Read, but the address moved 41

We reached the record at a different address than the one cited. The citation still resolves, but the final URL is recorded so a quiet relocation is visible.

List the 41 records
  1. claude.comHTTP 200
    https://claude.com/blog/cowork-web-mobile
    Anthropic1 citation
  2. claude.comHTTP 200
    https://claude.com/blog/working-at-the-frontier-cursor
    Anthropic1 citation
  3. developers.openai.comHTTP 200
    https://developers.openai.com/codex/models
    OpenAI Developers1 citation
  4. developers.openai.comHTTP 200
    https://developers.openai.com/codex/use-cases/follow-goals
    OpenAI Developers1 citation
  5. docs.anthropic.comHTTP 200
    https://docs.anthropic.com/en/docs/about-claude/models/overview
    Anthropic Docs1 citation
  6. docs.anthropic.comHTTP 200
    https://docs.anthropic.com/en/docs/about-claude/pricing
    Anthropic Docs1 citation
  7. help.openai.comHTTP 200
    https://help.openai.com/en/articles/11369540-using-codex-with-chatgpt
    OpenAI Help Center1 citation
  8. help.openai.comHTTP 200
    https://help.openai.com/en/articles/20001325-a-preview-of-gpt-56-sol-terra-and-luna
    OpenAI Help Center1 citation
  9. help.openai.comHTTP 200
    https://help.openai.com/en/articles/20001354-gpt-56-in-chatgpt
    OpenAI Help Center1 citation
  10. help.openai.comHTTP 200
    https://help.openai.com/en/articles/6825453-chatgpt-usage-limits
    OpenAI Help Center1 citation
  11. learn.chatgpt.comHTTP 200
    https://learn.chatgpt.com/codex/models
    OpenAI1 citation
  12. pokemongo.comHTTP 200
    https://pokemongo.com/en/gofest/global
    Pokémon GO1 citation
  13. sba.govHTTP 200
    https://sba.gov/article/2025/06/23/founder-lender-service-provider-convicted-role-multimillion-dollar-ppp-fraud-scheme
    U.S. Small Business Administration1 citation
  14. support.claude.comHTTP 200
    https://support.claude.com/en/articles/15424964-claude-fable-5-promotional-access
    Anthropic1 citation
  15. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/06/24/2026-12749/safety-standard-for-lithium-ion-batteries-used-in-micromobility-products-and-electrical-systems-of
    U.S. Consumer Product Safety Commission / Federal Register1 citation
  16. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/08/18/2026-16800/designation-of-databases-to-the-do-not-pay-working-system
    U.S. Department of the Treasury, Bureau of the Fiscal Service / Federal Register2 citations
  17. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/01/2026-17838/privacy-act-of-1974-system-of-records
    U.S. Department of Labor / Federal Register1 citation
  18. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/02/2026-17907/privacy-act-of-1974-matching-program
    U.S. Department of Health and Human Services / Federal Register1 citation
  19. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/02/2026-17963/privacy-act-of-1974-matching-program
    U.S. Department of Justice / Federal Register1 citation
  20. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/03/2026-18034/privacy-act-of-1974-matching-program
    U.S. Department of Agriculture / Federal Register1 citation
  21. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/11/2026-18527/privacy-act-of-1974-matching-program
    U.S. Small Business Administration / Federal Register2 citations
  22. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/15/2026-18801/privacy-act-of-1974-system-of-records
    U.S. Department of State / Federal Register1 citation
  23. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/16/2026-18978/federal-state-unemployment-compensation-uc-program-data-availability
    U.S. Department of Labor, Employment and Training Administration / Federal Register1 citation
  24. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/22/2026-19289/fleetcor-technologies-analysis-of-proposed-consent-order-to-aid-public-comment
    Federal Trade Commission / Federal Register1 citation
  25. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/23/2026-19493/patient-protection-and-affordable-care-act-temporary-moratoria-on-certain-agent-and-broker
    U.S. Department of Health and Human Services, Centers for Medicare & Medicaid Services / Federal Register1 citation
  26. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/24/2026-19579/substantial-product-hazard-list-amendments-to-requirements-for-window-covering-cords
    U.S. Consumer Product Safety Commission / Federal Register1 citation
  27. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/24/2026-19599/privacy-act-of-1974-matching-program
    U.S. Small Business Administration / Federal Register1 citation
  28. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/09/25/2026-19643/privacy-act-of-1974-matching-program
    U.S. Department of Health and Human Services, Centers for Medicare & Medicaid Services / Federal Register1 citation
  29. federalregister.govHTTP 200
    https://www.federalregister.gov/documents/2026/10/08/2026-20648/notice-of-intent-to-establish-a-negotiated-rulemaking-advisory-committee-for-vehicle-lighting
    National Highway Traffic Safety Administration (Federal Register)1 citation
  30. ftc.govHTTP 200
    https://www.ftc.gov/legal-library/browse/cases-proceedings/amway-ftc-v
    Federal Trade Commission1 citation
  31. justice.govHTTP 200
    https://www.justice.gov/letter-to-congress.pdf
    U.S. Department of Justice1 citation
  32. justice.govHTTP 200
    https://www.justice.gov/opa/media/1450606/dl?inline
    U.S. Department of Justice, U.S. Attorney's Office for the District of Rhode Island1 citation
  33. justice.govHTTP 200
    https://www.justice.gov/opa/media/1450611/dl?inline
    U.S. Department of Justice, U.S. Attorney's Office for the District of Rhode Island1 citation
  34. nist.govHTTP 200
    https://www.nist.gov/caisi
    National Institute of Standards and Technology1 citation
  35. paymentaccuracy.govHTTP 200
    https://www.paymentaccuracy.gov/
    U.S. Office of Management and Budget1 citation
  36. sba.govHTTP 200
    https://www.sba.gov/article/2025/11/21/co-founder-paycheck-protection-program-lender-service-provider-sentenced-10-years-prison-63m-covid
    U.S. Small Business Administration, Office of Inspector General1 citation
  37. sba.govHTTP 200
    https://www.sba.gov/article/2025/12/18/co-founder-paycheck-protection-program-lender-service-provider-sentenced-65m-covid-19-relief-fraud
    U.S. Small Business Administration1 citation
  38. sba.govHTTP 200
    https://www.sba.gov/article/2026/04/24/sba-sends-562000-suspected-fraudulent-loans-treasury-collections-totaling-22-billion
    U.S. Small Business Administration1 citation
  39. sba.govHTTP 200
    https://www.sba.gov/document/report-23-09-covid-19-pandemic-eidl-ppp-loan-fraud-landscape
    U.S. Small Business Administration, Office of Inspector General1 citation
  40. sba.govHTTP 200
    https://www.sba.gov/document/report-25-10-covid-19-pandemic-eidl-ppp-loan-fraud-landscape-recommendations-update
    U.S. Small Business Administration, Office of Inspector General1 citation
  41. sba.govHTTP 200
    https://www.sba.gov/document/report-protecting-integrity-pandemic-relief-programs
    U.S. Small Business Administration1 citation

Not at the address we cited 2

The address returned 404 or 410. This is the one outcome that should change how a reader treats the citation, and it is the queue this desk works from.

List the 2 records
  1. data.sec.govHTTP 404
    https://data.sec.gov/submissions/
    U.S. Securities and Exchange Commission1 citation
  2. support.claude.comHTTP 404
    https://support.claude.com/en/articles/15400594-claude-cowork-june-2026-usage-promotion
    Anthropic Help Center1 citation

Answered, but sent no document 30

The address returned a success status carrying no readable text — most often a bot-verification interstitial standing in for the page. It is recorded apart from a successful read because a status line is not a document, and apart from a decline because nothing here was refused. The citation is unverifiable from this desk until the document itself can be retrieved.

List the 30 records
  1. justice.govHTTP 200
    https://www.justice.gov/archives/opa/pr/boeing-charged-737-max-fraud-conspiracy-and-agrees-pay-over-25-billion
    U.S. Department of Justice, Office of Public Affairs1 citationanswered 200 with a bot-verification interstitial and no document text
  2. justice.govHTTP 200
    https://www.justice.gov/epstein
    U.S. Department of Justice1 citationanswered 200 with a bot-verification interstitial and no document text
  3. justice.govHTTP 200
    https://www.justice.gov/usao-cdca/pr/inland-empire-man-pleads-guilty-his-role-crime-ring-fraudulently-obtained-35-million
    U.S. Attorney's Office, Central District of California (DOJ), release 26-1751 citationanswered 200 with a bot-verification interstitial and no document text
  4. justice.govHTTP 200
    https://www.justice.gov/usao-cdca/pr/veteran-sentenced-3-years-federal-prison-defrauding-navy-out-more-9-million-bid
    U.S. Attorney's Office for the Central District of California1 citationanswered 200 with a bot-verification interstitial and no document text
  5. justice.govHTTP 200
    https://www.justice.gov/usao-ct/pr/connecticut-us-attorneys-office-announces-more-92-million-settlements-connected-ppp
    U.S. Attorney's Office for the District of Connecticut1 citationanswered 200 with a bot-verification interstitial and no document text
  6. justice.govHTTP 200
    https://www.justice.gov/usao-dc/pr/bitfinex-hacker-sentenced-money-laundering-conspiracy-involving-billions-stolen
    U.S. Attorney's Office, District of Columbia (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  7. justice.govHTTP 200
    https://www.justice.gov/usao-dc/pr/investigations-cryptocurrency-scams-result-seizure-more-25-million
    U.S. Attorney's Office, District of Columbia (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  8. justice.govHTTP 200
    https://www.justice.gov/usao-dc/pr/scam-center-strike-force-conducts-seizures-chinese-run-illicit-scammer-marketplace-and
    U.S. Attorney's Office, District of Columbia (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  9. justice.govHTTP 200
    https://www.justice.gov/usao-dc/pr/singaporean-ringleader-245-million-cryptocurrency-racketeering-enterprise-pleads-guilty
    U.S. Attorney's Office, District of Columbia (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  10. justice.govHTTP 200
    https://www.justice.gov/usao-edmi/pr/contractor-agrees-pay-one-largest-abilityone-program-related-false-claims-act
    U.S. Attorney's Office for the Eastern District of Michigan1 citationanswered 200 with a bot-verification interstitial and no document text
  11. justice.govHTTP 200
    https://www.justice.gov/usao-edpa/pr/dauphin-county-man-sentenced-10-years-prison-pandemic-unemployment-assistance-scheme
    U.S. Attorney's Office for the Eastern District of Pennsylvania1 citationanswered 200 with a bot-verification interstitial and no document text
  12. justice.govHTTP 200
    https://www.justice.gov/usao-edva/pr/eleven-defendants-sentenced-prison-hampton-roads-credit-union-parking-lot-scam
    U.S. Attorney's Office, Eastern District of Virginia (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  13. justice.govHTTP 200
    https://www.justice.gov/usao-md/pr/taiwan-led-manufacturer-agrees-515m-settlement-false-claims-act-and-administrative
    U.S. Attorney's Office for the District of Maryland1 citationanswered 200 with a bot-verification interstitial and no document text
  14. justice.govHTTP 200
    https://www.justice.gov/usao-mdfl/pr/goliath-ventures-ceo-pleads-guilty-cryptocurrency-fraud-scheme-conspiracy
    U.S. Attorney's Office, Middle District of Florida (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  15. justice.govHTTP 200
    https://www.justice.gov/usao-mdfl/pr/owner-semi-truck-business-indicted-operating-105-million-fraud-scheme
    U.S. Attorney's Office, Middle District of Florida (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  16. justice.govHTTP 200
    https://www.justice.gov/usao-sdin/pr/former-veterans-affairs-field-examiner-indicted-federal-fraud-charge-related-covid-19
    U.S. Attorney's Office, Southern District of Indiana (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  17. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/correctional-officers-charged-falsifying-records-august-9th-and-10th-metropolitan
    U.S. Attorney's Office, Southern District of New York1 citationanswered 200 with a bot-verification interstitial and no document text
  18. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/crypto-enabled-fraudster-sentenced-orchestrating-40-billion-fraud
    U.S. Attorney's Office, Southern District of New York (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  19. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/founder-celsius-sentenced-12-years-fraud-and-market-manipulation
    U.S. Attorney's Office, Southern District of New York (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  20. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/ghislaine-maxwell-charged-manhattan-federal-court-conspiring-jeffrey-epstein-sexually
    U.S. Attorney's Office, Southern District of New York1 citationanswered 200 with a bot-verification interstitial and no document text
  21. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/ghislaine-maxwell-sentenced-20-years-prison-conspiring-jeffrey-epstein-sexually-abuse
    U.S. Attorney's Office, Southern District of New York1 citationanswered 200 with a bot-verification interstitial and no document text
  22. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/jeffrey-epstein-charged-manhattan-federal-court-sex-trafficking-minors
    U.S. Attorney's Office, Southern District of New York1 citationanswered 200 with a bot-verification interstitial and no document text
  23. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/samuel-bankman-fried-sentenced-25-years-prison
    U.S. Attorney's Office, Southern District of New York (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  24. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/statement-us-attorney-damian-williams-verdict-us-v-ghislaine-maxwell
    U.S. Attorney's Office, Southern District of New York1 citationanswered 200 with a bot-verification interstitial and no document text
  25. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/two-robinhood-employees-charged-fraud
    U.S. Attorney's Office, Southern District of New York (DOJ), release 26-2601 citationanswered 200 with a bot-verification interstitial and no document text
  26. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/pr/us-attorney-seeks-forfeiture-61-million-cryptocurrency-iranian-militarys-black-market
    U.S. Attorney's Office, Southern District of New York (DOJ), release 26-2581 citationanswered 200 with a bot-verification interstitial and no document text
  27. justice.govHTTP 200
    https://www.justice.gov/usao-sdny/programs/victim-witness-services/united-states-v-jeffrey-epstein-19-cr-490-rmb
    U.S. Attorney's Office, Southern District of New York1 citationanswered 200 with a bot-verification interstitial and no document text
  28. justice.govHTTP 200
    https://www.justice.gov/usao-wdmo/pr/vietnamese-national-charged-role-massive-pig-butchering-cryptocurrency-scam
    U.S. Attorney's Office, Western District of Missouri (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  29. justice.govHTTP 200
    https://www.justice.gov/usao-wdtx/pr/flores-family-agrees-pay-additional-25-million-civil-penalties-defrauding-united
    U.S. Attorney's Office, Western District of Texas (DOJ)1 citationanswered 200 with a bot-verification interstitial and no document text
  30. justice.govHTTP 200
    https://www.justice.gov/usao-wdwa/pr/carnation-washington-man-sentenced-prison-covid-fraud-scheme-and-attempts-steal
    U.S. Attorney's Office for the Western District of Washington1 citationanswered 200 with a bot-verification interstitial and no document text

The server declined our automated request 29

The record exists and answered; it turned down an automated client. Bot filtering is an ordinary thing to run and implies nothing about the record's availability to a person, its accuracy, or the publisher's intent. This is a limit on this desk, not a finding about anyone.

List the 29 records
  1. api.gdeltproject.orgHTTP 429
    https://api.gdeltproject.org/api/v2/doc/doc
    The GDELT Project1 citation
  2. api.regulations.govHTTP 403
    https://api.regulations.gov/v4/documents?filter[docketId]=FTC-2026-1585
    eRulemaking Program, Regulations.gov (api.regulations.gov v4)1 citation
  3. thehill.comHTTP 403
    https://thehill.com/regulation/court-battles/5952687-justice-department-epstein-files-phang-suit/
    The Hill (Nexstar)1 citation
  4. axios.comHTTP 403
    https://www.axios.com/2026/07/08/gpt-sol-ultra-openai-anthropic-grok
    Axios1 citation
  5. courtlistener.comHTTP 403
    https://www.courtlistener.com/docket/15887848/united-states-v-epstein/
    CourtListener / RECAP1 citation
  6. courtlistener.comHTTP 403
    https://www.courtlistener.com/docket/16487310/united-states-v-noel/
    CourtListener / RECAP1 citation
  7. courtlistener.comHTTP 403
    https://www.courtlistener.com/docket/17318376/united-states-v-maxwell/
    CourtListener / RECAP1 citation
  8. courtlistener.comHTTP 403
    https://www.courtlistener.com/docket/29089563/united-states-v-the-boeing-company/
    Free Law Project (CourtListener / RECAP)1 citation
  9. courtlistener.comHTTP 403
    https://www.courtlistener.com/docket/66631291/united-states-v-bankman-fried/
    CourtListener / Free Law Project (RECAP mirror of PACER)2 citations
  10. courtlistener.comHTTP 403
    https://www.courtlistener.com/docket/73246595/phang-v-blanche/
    CourtListener / RECAP / U.S. District Court for the District of Columbia4 citations
  11. courtlistener.comHTTP 403
    https://www.courtlistener.com/docket/73721948/state-of-new-mexico-v-us-department-of-justice/
    CourtListener / RECAP1 citation
  12. disclosure.senate.govHTTP 403
    https://www.disclosure.senate.gov/
    U.S. Senate Office of Public Records1 citation
  13. faa.govHTTP 403
    https://www.faa.gov/newsroom/faa-statement-certification-boeing-737-max-7
    Federal Aviation Administration1 citation
  14. faa.govHTTP 403
    https://www.faa.gov/newsroom/statements/general-statements
    Federal Aviation Administration1 citation
  15. faa.govHTTP 403
    https://www.faa.gov/newsroom/updates-boeing-737-9-max-aircraft
    Federal Aviation Administration1 citation
  16. faa.govHTTP 403
    https://www.faa.gov/sites/faa.gov/files/2022-08/737_MAX_Timeline.pdf
    Federal Aviation Administration1 citation
  17. fcc.govHTTP 403
    https://www.fcc.gov/enforcement/orders
    Federal Communications Commission1 citation
  18. fdle.state.fl.usHTTP 403
    https://www.fdle.state.fl.us/regions-divisions/press-office
    Florida Department of Law Enforcement1 citation
  19. finance.senate.govHTTP 403
    https://www.finance.senate.gov/imo/media/doc/wyden_wall_street_epstein_report.pdf
    U.S. Senate Committee on Finance, Ranking Member1 citation
  20. finance.senate.govHTTP 403
    https://www.finance.senate.gov/ranking-members-news/continuing-epstein-investigation-wyden-releases-new-analysis-detailing-how-top-jpmorgan-chase-executives-enabled-epsteins-sex-trafficking-operation
    U.S. Senate Committee on Finance1 citation
  21. finance.senate.govHTTP 403
    https://www.finance.senate.gov/ranking-members-news/wyden-releases-new-report-on-failure-of-wall-street-banks-to-blow-the-whistle-on-jeffrey-epsteins-sex-trafficking-and-money-laundering-schemes
    U.S. Senate Committee on Finance, Ranking Member1 citation
  22. forbes.comHTTP 403
    https://www.forbes.com/sites/alisondurkee/2026/07/02/could-more-epstein-files-be-released-today-doj-faces-court-ordered-deadline-to-unredact-names/
    Forbes1 citation
  23. judiciary.senate.govHTTP 403
    https://www.judiciary.senate.gov/committee-activity/hearings/always-watching-flocks-nationwide-ai-surveillance-network
    U.S. Senate Committee on the Judiciary1 citation
  24. judiciary.senate.govHTTP 403
    https://www.judiciary.senate.gov/committee-activity/hearings/oversight-of-ai-rules-for-artificial-intelligence
    U.S. Senate Judiciary Subcommittee on Privacy, Technology, and the Law1 citation
  25. justice.govHTTP 403
    https://www.justice.gov/epstein/court-records
    U.S. Department of Justice1 citation
  26. mypalmbeachclerk.comHTTP 403
    https://www.mypalmbeachclerk.com/records/court-records/court-records-search
    Clerk of the Circuit Court & Comptroller, Palm Beach County1 citation
  27. nhtsa.govHTTP 403
    https://www.nhtsa.gov/recalls
    National Highway Traffic Safety Administration1 citation
  28. nhtsa.govHTTP 403
    https://www.nhtsa.gov/recalls?nhtsaId=26V481000
    National Highway Traffic Safety Administration (recall record and Mercedes-Benz USA filings)1 citation
  29. nhtsa.govHTTP 403
    https://www.nhtsa.gov/recalls?nhtsaId=26V578000
    National Highway Traffic Safety Administration (recall record and Ford filings)1 citation

We could not complete a connection 4

DNS, TLS, timeout, or socket failure. This may be the publisher, may be us, may be the network in between. It is not attributed to anyone.

List the 4 records
  1. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2025-07-28/pdf/2025-14217.pdf
    The White House / U.S. Government Publishing Office1 citationtimeout after 20000ms
  2. govinfo.govHTTP 200
    https://www.govinfo.gov/content/pkg/FR-2026-06-05/pdf/2026-11415.pdf
    The White House / U.S. Government Publishing Office1 citationtimeout after 20000ms
  3. oversight.govHTTP 406
    https://www.oversight.gov/boeing-charged-737-max-fraud-conspiracy-agrees-pay-25-billion
    Council of the Inspectors General on Integrity and Efficiency (Oversight.gov)1 citationunexpected status 406
  4. oversight.govHTTP 406
    https://www.oversight.gov/reports/federal
    Council of the Inspectors General on Integrity and Efficiency1 citationunexpected status 406

Not yet checked 7

Cited but not covered by the most recent probe run — usually an anchor added after the last sweep.

List the 7 records
  1. consumerfinance.gov
    https://www.consumerfinance.gov/about-us/newsroom/cfpb-announces-new-initiative-to-address-occ-uncovered-debanking-by-large-banks/
    Consumer Financial Protection Bureau1 citation
  2. cpsc.gov
    https://www.cpsc.gov/Recalls/2027/Costway-Recalls-Convertible-High-Chairs-Due-to-Risk-of-Serious-Injury-or-Death-from-Entrapment-and-Fall-Hazards-Violate-Mandatory-Standard-for-High-Chairs
    U.S. Consumer Product Safety Commission1 citation
  3. cpsc.gov
    https://www.cpsc.gov/Warnings/2027/CPSC-Warns-Consumers-to-Stop-Using-PowRyte-Pressure-Washers-Immediately-Due-to-Serious-Shock-and-Electrocution-Hazards-Risk-of-Serious-Injury-or-Death
    U.S. Consumer Product Safety Commission1 citation
  4. cpsc.gov
    https://www.cpsc.gov/Warnings/2027/CPSC-Warns-Consumers-to-Stop-Using-Reliancer-Adult-Portable-Bed-Rails-Immediately-Due-to-Risk-of-Serious-Injury-or-Death-from-Entrapment-and-Asphyxiation-Violate-Mandatory-Standard-for-Adult-Portable-Bed-Rails
    U.S. Consumer Product Safety Commission1 citation
  5. ftc.gov
    https://www.ftc.gov/system/files/ftc_gov/pdf/GovAssist-Complaint.pdf
    Federal Trade Commission1 citation
  6. ftc.gov
    https://www.ftc.gov/system/files/ftc_gov/pdf/Riverside-Complaint.pdf
    Federal Trade Commission and State of Washington1 citation
  7. ftc.gov
    https://www.ftc.gov/system/files/ftc_gov/pdf/Riverside-Order.pdf
    Federal Trade Commission and State of Washington1 citation

What a source can settle

Every claim on this site cites a page, and this desk re-reads those pages to check the claims still hold. Whether that re-read can settle anything is a property of the source, not of the claim — and a reader has no way to tell which sources can bear the weight put on them. Three questions decide it, and each is measured by an instrument whose output is published above.

  1. Can this desk read it?519 of 584

    65 cited sources decline this desk’s automated reads, answer without sending the document, no longer resolve, or did not answer at all. A claim citing one of those rests on the single reading taken when it was anchored, and on nothing since. It is not wrong; it is unrepeatable.

  2. Would a change to it be visible?519 not comparable

    A page is comparable when this desk holds a fingerprint of its visible text to diff the next reading against. Where it does not, an edit to the exact sentence being cited would pass unseen — the citation would still resolve, and would no longer say what it is cited for.

  3. Does it ever say the thing happened?7 of 7 do

    Of the pages carrying dated commitments, all state at least one of them as done. A page that schedules but never settles cannot be read for an outcome after its date, and its future tense is not evidence that nothing happened. This was measured on 2026-08-27 after a record on this site drew exactly that wrong inference and had to be corrected.

How this was measured

Last sweep
— 12 days ago (stale; treat as historical)
Method
HEAD then GET, following redirects.
Change detection
sha256 of visible text, markup and scripts stripped. Hashing raw bytes would be useless — large publishers embed a build id or rotating asset hash, so a byte hash changes on every fetch and would report constant drift. Only the words are compared.
Politeness
One request per record, at most 5 at a time, never two at once to the same host, with 900ms between requests to any one publisher. The crawler identifies itself and links back here.
Not counted as checked
7 cited records were added after the last sweep. They stay in the denominator rather than being dropped, so this page cannot flatter itself by only counting what it managed to reach.