EVIDENCE FILE // OCTOBER 31, 2026
OpenAI and Wikimedia Fair Use Evidence File: Two Documents, One Deadline
Claim-level evidence for the report “OpenAI and Wikimedia Both File on Fair Use, From Opposite Sides”. Every quotation in that article was checked against a saved copy of the document it is attributed to, by a harness with negative controls. This file records what was captured, what each claim rests on, and what the reporting does not establish.
Documents relied on
Each document was retrieved directly over HTTPS and saved before any quotation was tested, so that every claim is pinned to a fixed object rather than to a page that may change. Digests are SHA-256 of the saved file.
| Document | URL | Retrieved | Size | SHA-256 (first 16) |
|---|---|---|---|---|
| OpenAI, “Fair use benefits everyone” | openai.com/index/fair-use-benefits-everyone/ | HTTP 200 | 409,038 bytes | EF270CB7954849CF |
| Wikimedia Foundation amicus announcement | wikimediafoundation.org/news/2026/10/30/wikimedia-foundation-amicus-brief-new-york-times-v-open-ai-case/ | HTTP 200 | 172,065 bytes | 77BD98866E402608 |
| CAIDP, “AI Training and Copyright” case tracker | caidp.org/cases/openai-copyright-infringement/ | HTTP 200 | 109,940 bytes | 64204FB676493EBF |
Method
Two independent checks were run, because a single check that passes tells you less than two that agree.
- A named-quotation check. A fixed list of every string the article attributes to a source was tested verbatim against the saved capture, alongside seven negative controls: sentences that must not be found in the document. All attributed strings were found; every negative control was correctly absent. The controls are what make a pass meaningful, since a search that matches everything would otherwise look like success.
- A whole-article extraction audit. Rather than trust the hand-written list, this check reads the published HTML, pulls out every span the article sets as a quotation, and requires each one to appear verbatim in at least one captured document. This is a coverage net: it would catch a quotation that was written into the article but never added to the list. Result for this story: six substantive quotations checked, six found, none missing, with two page headings declared in advance as internal references rather than source quotations (“Fair Use Benefits Everyone” and “United States Government”).
Both checks normalise markup, typographic quotes and dashes, non-breaking spaces, word-joiner and soft-hyphen characters, and whitespace, because those differences are transport artefacts rather than differences in what a document says. They do not normalise words.
Claim-level table
| Claim in the article | Rests on | Status |
|---|---|---|
| Amicus deadline was October 30, 2026, extended from October 16 | CAIDP tracker text, read directly | Verified against the tracker, not the docket |
| Court order inviting amicus briefs at ECF No. 62, dated August 7, 2026 | CAIDP tracker citation | Verified as a tracker record; docket not read |
| OpenAI published its page on October 30, 2026 | Date displayed on the page | Verified |
| OpenAI’s framing of the Times’ lawsuit (the “undeserved payday” passage) | Verbatim quotation from the OpenAI page | Found verbatim; presented as a party’s allegation, never as fact |
| “The Court should reject Plaintiffs’ attempt to extend copyright beyond its established limits” sits under a heading reading “AI Progress” with no filer named | OpenAI page markup and surrounding text | Found verbatim; attribution corrected before publication |
| The page separately carries a “United States Government” section with different text | OpenAI page | Verified; this is what the correction rests on |
| United States filed a Statement of Interest on September 1, 2026, not an amicus brief on October 30 | CAIDP tracker entry, dated in the page markup | Verified as a tracker record. The tracker shows no US amicus brief on October 30; that is not proof none was filed |
| Wikimedia split: fair use for training, licence obligation for retrieval | Foundation announcement, verbatim quotation with the omitted clause marked by an ellipsis | Found verbatim after normalisation |
| No ruling on fair use exists in this litigation | Absence across all three captured documents | Reported as absence, not as confirmation. We did not search the docket |
Negative controls
Seven strings were written to be plausible and false, then required to be absent from the combined text of the three captures that stage searched: OpenAI’s signal announcement, Google’s Search Central post and the Internet-Draft. The attribution control feeds back into this story’s correction: the article’s earlier claim, that the “reject Plaintiffs’ attempt” sentence sits under a United States Government heading, has the shape that control tests for, and the capture does not support it. They target the exact errors this story could have made: that OpenAI has already shipped the signal, that Google will honour it in 2026, that the draft’s policy token is a directive for crawling, a non-existent token name, an invented registration identifier, the false attribution “The United States Government should reject Plaintiffs”, and an invented absolutist reading of Wikimedia’s position. All seven were correctly absent. If any had been “found”, the checks above would have been treated as unreliable and the article withheld rather than published.
The attribution correction
An earlier revision attributed “The Court should reject Plaintiffs’ attempt to extend copyright beyond its established limits” to United States Government filings. The page does not support that. The sentence sits under a heading reading “AI Progress”, and the separate “United States Government” section contains different text about narrowing the fair use doctrine. The published article makes no such attribution, states what the page actually shows, and records the correction here rather than removing the trace of it.
What this article does not claim
- It does not report or predict a ruling. No decision has been found.
- It does not say the United States filed an amicus brief on October 30. It says an independent tracker records a September Statement of Interest and no October amicus brief.
- It does not name the filer behind the “AI Progress” excerpt, because the page does not name one.
- It does not claim only two documents were filed on October 30. Two were verified; the volume and identity of the rest is unknown.
- It does not treat OpenAI’s characterisation of its opponents as established fact.
Production record
| Stage | Performed by | Outcome |
|---|---|---|
| Capture | Computer, Newsroom Lead | Three documents saved; HTTP 200 each; sizes recorded |
| Drafting | Computer, Newsroom Lead | Three revisions; one material attribution error found and corrected |
| Named-quotation check with controls | Quotation harness | All attributed strings found; seven controls absent |
| Whole-article extraction audit | Quotation harness | 6 of 6 substantive quotations found; 0 missing; 2 declared internal references |
| Publication authority | Human publisher | Authorised October 31, 2026, with the synopsis signed off |
Known limits of this package
The docket was not read. That is the largest single gap in this story: every procedural date comes from a third-party tracker rather than the court file, and a reader who needs the primary record should go to the docket. The evidence here is strong on what the two documents say and adequate, not conclusive, on procedure.