EU AI Act update, 8 May 2026: current law remains the baseline. The Digital Omnibus provisional agreement would move many high-risk AI obligations to 2 Dec 2027 and product-integrated high-risk AI rules to 2 Aug 2028 if formally adopted. Track status EU AI Act update: current law remains the baseline. Digital Omnibus dates apply only if formally adopted. Track status

Blog · March 2026 · 8 min read

LAW VS SOFT LAWSeparate the binding article from the voluntary code

Article 50 Code vs Article 50 Law: What the Draft Code Covers — and What It Does Not

Article 50 timing watch

Do not treat every Article 50 obligation as postponed. The current published AI Act baseline still requires separate review for Article 50 transparency duties. The official 7 May 2026 Digital Omnibus provisional agreement specifically tracks a 2 December 2026 planning date for watermarking and technical solutions for AI-generated content if formally adopted and published.

Executive Summary

The market is using “Article 50” and “Article 50 Code of Practice” as if they were interchangeable. They are not. Article 50 is law. The Code of Practice is a voluntary compliance tool under development.

If you collapse those two layers, you will either overstate what the draft Code does or under-prepare for the obligations that already exist in the Article itself.

Executive compliance dashboard separating binding Article 50 legal duties from voluntary code provisions for AI-generated content marking and labelling
The right model is simple: law first, code second. Not the other way around.

What the law covers

Article 50 contains multiple transparency obligations. In practice, most businesses need to think in four buckets:

Article 50 areaBinding statusWho it affects
Article 50(1)LawAI systems intended to interact directly with natural persons.
Article 50(2)LawProviders of systems generating synthetic audio, image, video, or text content that must be machine-readable and detectable as artificially generated or manipulated.
Article 50(3)LawEmotion recognition and biometric categorisation contexts requiring notice to affected persons.
Article 50(4)LawDeepfake and certain public-interest AI-generated text labelling duties.

What the Code covers

The Commission’s own policy page is explicit: the final Code, if approved, is intended as a voluntary tool to demonstrate compliance with Article 50(2) and 50(4). It is not a complete operational guide to every aspect of Article 50. The second draft was published on 5 March 2026. As of the 5 May 2026 review, final approval had not been verified in the official source set used for this page.

That matters because many summaries online imply the Code defines the whole article. It does not. The Code is focused on marking and labelling AI-generated content, with cross-cutting consideration of information to natural persons under Article 50(5). It supports compliance; it does not replace the legal obligations in Article 50.

Three-panel legal architecture visual showing Article 50 law, voluntary code of practice, and implementation workflow for content provenance and public disclosure
The Code is a tool to support parts of the law. It is not the law itself.

Why this distinction matters

What businesses should do now

Step 1: map which of the Article 50 buckets apply to your systems. Step 2: build your mandatory law baseline around system notices, machine-readable marking, and deepfake/public-interest disclosure. Step 3: use the draft Code only as a design aid for the 50(2)/50(4) workflow, not as a replacement for legal interpretation.

For a more detailed operational view, see our Article 50 second-draft analysis and the Transparency Validator.

About the author: Abhishek G Sharma is the founder of Move78 International Limited.

Disclaimer: This page is educational and operational guidance only. It is not legal advice. Published: March 2026. Reviewed through 3 May 2026.

Official sources checked

Need More Practical Guidance?

Explore the free EU AI Compass tools and guides to classify your use case, understand your obligations, and move to the next compliance step.