EU AI Act Weekly Radar: Transparency Code advances as training-data governance moves into focus

This week’s lextrace roundup brings together two European Commission updates that matter for teams building, deploying, or governing generative AI in the EU.

First, the Commission has issued a positive opinion on the Code of Practice on Transparency of AI-generated content, concluding that the voluntary code adequately covers the obligations in AI Act Article 50(2), (4) and (5). According to the Commission’s library page for the opinion, the AI Board adopted its adequacy assessment the following day, and providers and deployers of generative AI systems are being invited to sign ahead of Article 50 applying on 2 August 2026.

Second, the Commission has published a feasibility study on an EU-level registry for text-and-data-mining opt-outs. The study concludes that such a registry could be technically and policy feasible as a complement to existing tools, helping rightsholders express reservations while also helping AI developers identify those reservations.

Taken together, these developments show the EU implementation story becoming more operational. One update is about a near-term compliance route for transparency duties. The other is about the infrastructure that could shape how AI developers handle copyright-related training data reservations. For governance teams, that is a useful pairing: the EU is not only specifying obligations, but also exploring the mechanisms that could make them more manageable in practice.

1) The clearest immediate signal: Article 50 transparency is moving from principle to process

The most actionable item this week is the Commission’s opinion on the Code of Practice on Transparency of AI-generated content.

Based on the Commission’s summary, the opinion finds that the voluntary code adequately covers the relevant obligations under Article 50(2), (4) and (5) of the AI Act. The same summary also notes that the AI Board adopted its adequacy assessment the next day, and that providers and deployers of generative AI systems are invited to sign before the transparency rules begin to apply on 2 August 2026.

For companies working with generative AI, this matters for three reasons.

A. It points to a concrete implementation path

The AI Act has often been discussed at the level of legal categories and future obligations. A Commission-backed adequacy opinion changes the conversation. It suggests that affected organizations now have a more tangible benchmark for how to operationalize upcoming transparency duties.

That does not make the code itself a substitute for the law. But it does indicate that the Commission sees the code as an adequate way to cover the specified Article 50 requirements. In practical governance terms, that is a strong signal for legal, product, and compliance teams deciding what to build into deployment processes over the next few weeks.

B. It raises the importance of deployer readiness, not just provider readiness

The Commission summary expressly refers to providers and deployers of generative AI systems being invited to sign. That is notable because EU AI Act preparation is often framed primarily as a provider issue.

This update reinforces a broader governance lesson: transparency compliance for generative AI can involve downstream deployment decisions, user-facing disclosures, and operational controls, not just model development. Organizations integrating third-party generative AI into products or workflows should be treating Article 50 readiness as part of their own compliance planning.

C. The implementation clock is now short

The Commission’s publication highlights 2 August 2026 as the date on which Article 50 applies. That turns transparency compliance from a medium-term agenda item into an immediate execution task.

For many organizations, the most relevant question is no longer whether Article 50 will matter, but whether internal controls, product disclosures, content labeling flows, vendor commitments, and governance documentation are aligned in time.

2) Why this matters beyond pure legal interpretation

Even from the limited facts released in the Commission summary, the policy direction is clear: the EU is using codes and institutional assessments to reduce ambiguity around implementation.

That matters because the hardest part of AI governance is often not identifying a rule, but translating it into repeatable business process. When the Commission states that a transparency code adequately covers particular AI Act obligations, it effectively gives the market a focal point.

For lextrace readers, the practical implication is that governance teams should expect Article 50 compliance discussions to become more standardized. Internal debates may increasingly shift from "what do the rules probably mean?" to "how closely do our controls map to the code the Commission has endorsed?"

That kind of standardization can be especially important for:

• enterprise procurement teams evaluating generative AI vendors,
• product counsel reviewing user disclosure mechanisms,
• compliance teams building evidence trails,
• and deployers seeking assurance that upstream providers are supporting downstream transparency obligations.

3) The second signal: training-data governance is becoming more infrastructural

The other important development this week is the Commission’s publication of the feasibility study for introducing an EU-level registry of Text and Data Mining opt-out.

According to the Commission’s summary, the study concludes that a registry could be both technically and policy feasible. It would not replace existing opt-out tools, but could complement them by helping rightsholders express reservations and helping AI developers identify those reservations. The Commission says it will consider next steps together with ongoing EUIPO work.

This is not framed as a direct AI Act implementation measure in the source material. Still, it is highly relevant to the wider EU AI compliance environment.

A. It addresses a recurring operational problem

One of the practical challenges in AI training-data governance is not just the existence of rights reservations, but the discoverability and usability of those reservations at scale.

A registry concept speaks directly to that problem. If a centralized or coordinated mechanism makes opt-outs easier to express and easier to identify, it could materially affect how model developers structure ingestion, filtering, documentation, and ongoing compliance monitoring.

B. It could reshape expectations for documentation and diligence

If the EU ultimately moves toward a registry-supported ecosystem, developers may face stronger expectations around checking, recording, and responding to reservations. Even before any concrete new mechanism is adopted, the publication of a feasibility study signals that policymakers are thinking about the practical plumbing of training-data governance.

For organizations building foundation models or other large-scale generative AI systems, that has implications for:

• data sourcing governance,
• rights-reservation detection workflows,
• training corpus documentation,
• supplier and dataset due diligence,
• and auditability of decision-making.

C. It fits the broader compliance trend toward systematization

This week’s two updates are connected by a common theme: the EU is moving from broad normative expectations toward operational structures.

In the transparency context, that structure is a code assessed as adequate for certain Article 50 duties. In the text-and-data-mining context, it is a possible registry architecture that could make reservations easier to manage. Both developments point toward a compliance environment where organizations will increasingly be expected to show process maturity, not just policy awareness.

4) The bigger story: implementation is becoming layered

If you step back, these updates suggest that EU AI regulation is developing across multiple layers at once.

Layer 1: Legal obligations

The AI Act sets formal duties, including transparency obligations that the Commission says will apply from 2 August 2026 for the Article 50 items referenced in this week’s update.

Layer 2: Governance instruments

The transparency code appears to function as a practical governance instrument that can help organizations map those duties into operational commitments.

Layer 3: Supporting compliance infrastructure

The text-and-data-mining opt-out registry study points to a possible infrastructural layer: tools or systems that can make compliance more scalable and less fragmented.

For professional audiences, this layered view is useful because it reflects how real compliance programs are built. Few organizations comply with major digital regulation by reading statutory language alone. They rely on codes, standards, workflows, interfaces, recordkeeping, and market expectations. This week’s Commission publications reinforce that reality.

5) What providers and deployers should be doing now

Based on these updates alone, there are several practical questions worth asking internally.

For providers and deployers of generative AI systems

• Have we reviewed whether the Code of Practice on Transparency of AI-generated content aligns with our current controls?
• Do our user-facing interfaces, disclosures, and content handling processes appear ready for the Article 50 obligations referenced by the Commission?
• If we rely on third-party models or tools, have we clarified which transparency responsibilities sit with the provider and which fall on us as deployer?
• Do we have a documented decision on whether to sign the code, and if not, who owns that decision?

For model developers and training-data governance teams

• Are our current workflows capable of identifying and honoring text-and-data-mining reservations at scale?
• How fragmented are our current sources of rights-reservation information?
• Would a future registry-based approach require changes to ingestion pipelines, vendor controls, or recordkeeping?
• Are we treating training-data governance as a one-time legal review, or as an ongoing operational control environment?

For legal and compliance leadership

• Do our AI governance programs distinguish clearly between near-term obligations that are now close to application and longer-term infrastructure changes that may alter best practice?
• Are we prepared to evidence not just policy intent, but implementation choices?
• Have we assigned ownership for monitoring Commission and EUIPO follow-up on the text-and-data-mining registry discussion?

6) What this week does not resolve

These Commission updates are important, but they do not answer every open question.

The transparency opinion, as summarized by the Commission, tells the market that the code adequately covers specified Article 50 obligations. It does not, on its own, settle every interpretive issue that companies may face in different product contexts.

Likewise, the text-and-data-mining registry study signals direction rather than immediate new obligations. A feasibility finding is not the same as a final policy decision or implemented registry.

That distinction matters. Governance teams should treat this week as a strong indicator of regulatory direction and practical preparation needs, while avoiding the mistake of reading exploratory infrastructure work as already-final law.

7) lextrace take: expect the next phase of EU AI compliance to be more operational and more evidenced

The most important takeaway from this week is not simply that the Commission published two AI-relevant documents. It is that both documents point to the same implementation pattern.

The EU AI compliance environment is becoming more operational, because organizations are being given more concrete mechanisms for translating obligations into practice.

It is also becoming more evidenced, because codes, registries, and process-driven governance models make it easier for regulators, counterparties, and internal auditors to ask a harder question: not whether a company knows the rule, but whether it can show how it implemented it.

For generative AI providers and deployers, the immediate focus should be transparency readiness ahead of 2 August 2026, using the Commission-backed code as a critical reference point.

For model developers and data governance teams, the text-and-data-mining opt-out study is a reminder that training-data compliance is unlikely to remain a purely abstract policy debate. The EU is exploring the practical machinery that could shape future expectations.

That combination makes this a consequential week in the AI Act rollout: one update narrows uncertainty around a near-term compliance obligation, while the other previews how the broader governance ecosystem around AI development may continue to mature.