Verification note (2026-10-09): the Commission’s own pages were re-read from this network on 2026-10-09: the guidelines page “Guidelines on transparency obligations for providers and deployers of AI systems” (Publication 20 July 2026, Last update 31 July 2026) states that “These transparency obligations apply from 2 August 2026” and that “The Commission adopted these guidelines”; the Commission-opinion page for the Code of Practice on Transparency of AI-generated Content (Publication 09 July 2026, Last update 31 July 2026) describes the voluntary code and the Commission’s assessment. What the pages do not do is decide how the obligations apply to a specific product or output — that still has to be read from the individual Article 50 provisions and your own use case.
Short answer: The Commission’s own pages state that the AI Act’s Article 50 transparency obligations apply from 2 August 2026, and the Commission has adopted guidelines on their scope (guidelines page published 20 July 2026, re-read 2026-10-09). The Commission also describes the voluntary Code of Practice on Transparency of AI-generated Content as an effective means to facilitate compliance, following its assessment. Teams that expose AI interaction or AI-generated content to EU users should settle their disclosure and marking approach now; whether a specific obligation binds your product still depends on the individual Article 50 provisions.
What happened
Two related decisions landed in the final stretch before the deadline:
- Guidelines on the scope of Article 50. The Commission has published “Guidelines on transparency obligations for providers and deployers of AI systems” (Publication 20 July 2026, Last update 31 July 2026); the page states that the Commission adopted these guidelines and that the transparency obligations “apply from 2 August 2026” (library page).
- Code of Practice on Transparency of AI-generated Content. The Commission’s opinion page (Publication 09 July 2026, Last update 31 July 2026) says the Commission and the AI Board consider this voluntary code an effective means to facilitate compliance with the AI Act’s transparency obligations, and that on 8 July the Commission concluded its assessment (opinion page).
The context: the political agreement on the AI Omnibus extends the high-risk transition dates — Annex III use cases to 2 December 2027 and Annex I embedded-product rules to 2 August 2028 — and the Commission’s framework page states the Omnibus entered into force on 27 July 2026. Article 50 transparency obligations were not part of that postponement; 2 August 2026 stands for them.
Who in engineering is actually affected
Article 50 is not aimed only at consumer chatbots. Engineering organizations should map at least three exposure paths:
| Exposure | Typical example | Question to answer before August 2 |
|---|---|---|
| AI systems interacting with people | A support or coding assistant embedded in your product for EU users | Is the AI nature of the interaction disclosed where it is not obvious? |
| AI-generated content shown to users | Generated text, code explanations, images, or summaries surfaced in your product | Are marking/labelling obligations met per the Commission’s Code of Practice? |
| Internal tools reaching external users | An internal agent whose output ships into customer-facing surfaces | Does the output path carry the required transparency downstream? |
AI coding tools used purely internally are generally a governance rather than an Article 50 problem — but output that flows into user-facing products can change that analysis. This is a legal determination; route it through counsel with a concrete inventory of your AI touchpoints. Our EU AI Act timeline guide covers the broader schedule.
What to do this week
- Inventory AI touchpoints that face EU users: interactions, generated content, and any surfaces where AI output is republished.
- Read the guidelines on the scope of Article 50 against your inventory (library page).
- Adopt or map to the Code of Practice for content marking; the Commission describes signatories as able to rely on its measures to demonstrate compliance after the positive assessment.
- Document decisions. Regulators ask for evidence trails, and so do enterprise customers. Keep the same discipline you would apply to a governance program for AI coding tools.
A 60-minute readiness pass
If August 2 is close and you have not started, this bounded pass gets a first draft of the evidence regulators and enterprise customers ask for. It is triage, not a substitute for legal review.
- List AI touchpoints (20 min). Enumerate every place your product interacts with EU users through AI or shows them AI-generated content. Include embedded assistants, generated summaries, and any internal agent whose output reaches customers.
- Classify each against Article 50 (15 min). For each touchpoint, note whether it is direct AI interaction, generated content, or out of scope, and why. Flag anything ambiguous for counsel rather than guessing.
- Check disclosure and marking (15 min). Where the AI nature is not obvious, confirm a disclosure exists; where content is generated, confirm marking maps to the recognized Code of Practice.
- Record the decisions (10 min). Capture the inventory, classifications, and gaps in one document with an owner and a date. That record is the artifact both regulators and enterprise buyers request.
The output is not a compliance certificate — it is a defensible starting point that turns a vague deadline into a short, owned punch list.
What this signals beyond August 2
How the dates moved is the planning signal: the Omnibus extended the high-risk classification dates while the transparency date stayed at 2 August 2026 (Commission pages, re-read 2026-10-09). The most concrete, low-ambiguity obligations have proved the least likely to be postponed; an inventory you keep current is cheaper than a deadline scramble.
The takeaway
The Omnibus bought time for high-risk classification work — not for transparency. If your product interacts with EU users through AI or shows them AI-generated content, 2 August 2026 is the date the Commission states, and the Article 50 guidelines plus the voluntary Code of Practice are the compliance map; how each obligation lands on your product still needs the individual provisions.