The Omnibus Trilogue Failed (April 2026): A Post-Mortem

What happened

The Cypriot Presidency of the Council convened a political trilogue on the Digital Omnibus on AI on 28 April 2026. The session ended without an agreed text after roughly twelve hours of negotiation (Bird & Bird).

Both the European Parliament (which voted 569–45–23 on 26 March) and the Council (general approach adopted 13 March) had entered the trilogue with mandates broadly supporting the Commission’s proposal to defer high-risk deadlines. The expectation across the regulatory advisory community was that the trilogue would produce a political agreement the same night. It did not.

At the time, a follow-up trilogue was expected in early-to-mid May 2026. It took place on 7 May and produced agreement; the later enactment is recorded in the editor's note above.

Why it failed

The sticking point was conformity assessment architecture for AI embedded in regulated products — specifically, whether AI components in products covered by Annex I Section A (machinery, medical devices, civil aviation, etc.) should undergo conformity assessment under existing sectoral legislation or under a new AI Act–specific procedure (Bird & Bird).

The Parliament favoured deferring to sectoral law: if a medical device already goes through CE marking under the Medical Devices Regulation, the AI component should be assessed as part of that existing process. The Council resisted, arguing that this approach creates gaps where sectoral bodies lack AI-specific competence. The Commission occupied a middle position. Neither side moved enough to close the gap in the available time.

This is not a cosmetic disagreement. The conformity assessment question determines which notified bodies assess AI risk, which standards apply, and how compliance costs are distributed across supply chains. It was always the hardest open issue in the Omnibus, and it remains unresolved.

What this means for the deadline

At the time this April account was written, the original 2 August 2026 date in Article 113 remained the legal position. That statement was superseded when Regulation (EU) 2026/1744 entered into force on 27 July 2026.

At the time (late April 2026), several regulatory advisors were recommending that organisations prepare against the original August 2026 deadline. Modulos and Bird & Bird both take this position. Even if the mid-May trilogue succeeds, the remaining legislative steps (legal-linguistic review, formal Council and Parliament adoption, Official Journal publication) take weeks. The margin for the Omnibus to enter into force before 2 August is now extremely thin.

What to do now

Establish your risk classification with regula check ., run a gap assessment against Articles 9–15 with regula gap ., build your documentation scaffolding with regula docs ., and track the next trilogue outcome. Starting the technical documentation and risk management work now buys time on the harder obligations regardless of which deadline ultimately applies.

1. Establish your risk classification

   Run regula check . in your project root. This scans your codebase against 419 risk patterns and returns indicators for human review; it cannot legally classify the AI system because Article 6 classification also depends on intended purpose and deployment context. If your reviewed classification is not high-risk, the deadline question is less urgent — but Article 5 prohibitions and Article 50 transparency obligations are already in force regardless.

2. Run a gap assessment against Articles 9–15

   Run regula gap . to see where the evidence sits. It reports a decision of insufficient_information until the applicability facts are settled, names the facts it still needs, and attaches article evidence only where the decision kernel resolved the matching obligation. It does not score you per article and it does not estimate effort, because neither follows from reading code. See our decision framework for how to prioritise across the three compliance tracks.

3. Build the documentation scaffolding now

   Articles 11 and 12 require technical documentation and automatic logging. These take time but are straightforward to start. Run regula docs . to generate an Annex IV documentation template pre-filled from your actual codebase. Starting the documentation now buys you time on the harder obligations (risk management under Article 9, human oversight under Article 14).

4. Track the next trilogue

   The follow-up trilogue subsequently succeeded on 7 May 2026. Regula’s delta log tracks regulatory changes with primary sources. Run regula regwatch to check whether your installed ruleset reflects the latest recorded state.

Where Regula fits

Regula is a static code scanner that identifies regulatory risk indicators and generates documentation scaffolds. It does not determine legal classification, decide which obligations apply, replace legal advice, or monitor legislation in real time. It provides code-level evidence for contextual review. For historical background on the proposal, see: The EU AI Act Omnibus Delay: What Developers Actually Need to Know.

Last reviewed: 14 August 2026 · Author: Kuziva Muzondo · Not legal advice. Regula identifies risk indicators for developer review.

Related reading

• The EU AI Act Omnibus delay — Full timeline, deadline table, and risk-tier-specific guidance
• Omnibus decision framework — Three-track planning approach for deadline uncertainty
• Why startups are ignoring the AI Act — Three triggers that change the calculus for founders

Discuss on Hacker News