DEV Community

stepinto.dev
stepinto.dev

Posted on Edited on Originally published at stepinto.dev

Article 50 of the AI Act, Annotated Clause by Clause

Article 50 is the part of the AI Act that most software teams meet first. It has applied since 2 August 2026, and the one grace period it got, for marking the output of generative systems already on the market by then, ends on 2 December. It is also short enough to read in full, so that is the format: the article verbatim below, every clause of it selectable, and the notes in the panel beside it.

Each clause has a plain reading of what it means. On top of that sit notes of five kinds, each with its own colour: what it changes in software, what is contested, what the Commission's guidance says, where it connects to the rest of the law, and dates. On a phone, tap a clause and the notes slide up from the bottom. With a keyboard, Tab moves through the clauses, and once one is open, j and k step forwards and back. Every clause and every note has its own link, so you can send someone straight to the sentence you are arguing about.

Two documents from the summer do most of the interpreting. The Commission's guidelines on Article 50 came out on 20 July 2026, and the Code of Practice on Transparency of AI-Generated Content was finalised on 10 June and has since been assessed as adequate by the Commission and the AI Board. The notes cite both by paragraph or measure number, so every claim can be checked against the source.

If you only open three clauses, make them these. The design duty in paragraph 1, because a line in your terms and conditions does not meet it. The marking duty in paragraph 2, because if your product calls a model API and shows the result under your name, the duty is yours. And the standard editing exception, because whether an output needs a mark depends on which feature produced it, so the decision lives in your code.

The notes keep growing after today. Each one is dated, and the log at the foot of the page lists what was added when. The compliance-as-code post from February now carries a dated note pointing here, since its middleware numbered the paragraphs differently from the way the guidelines read them.

This is an engineer's reading and no substitute for legal advice. Lawyers I know are reviewing it, and their corrections will appear in the notes with their dates.

Top comments (0)