The August Deadline Is Alive — But 'In Effect' and 'Enforced' Are Two Different Things

Let's start with what happened on April 28 and what it actually proves. The EU Parliament's IMCO/AIGE joint committee passed its negotiating mandate on the Digital Omnibus by a reported 101-9 margin — that's the Parliament staking out its internal position in favor of extending the high-risk deadline to December 2027. The Council adopted its own general approach on March 13. Both institutions want delay. But trilogue — the interinstitutional negotiation between Parliament, Council, and Commission — did not conclude before April 28. The April 28 date mattered because it was the last realistic window before summer recess for a deal to be ratified and transposed before August 2. That window has now closed.

This is proximate evidence of legislative stall, not direct evidence that the deadline survives enforcement. Here's the distinction that matters: the 101-9 committee vote tells us Parliament's internal negotiating position is nearly unanimous in favor of delay. It does not tell us that trilogue will fail entirely — only that it didn't finish in time for a clean pre-August resolution. The Council and Parliament could still reach a political agreement that is applied provisionally or retroactively. We've seen this in EU legislative history before. So the August 2 date being 'in legal effect' right now is real, but it's not the same as saying enforcement actions will flow from it on August 3.

Now to a counterargument we need to take more seriously than our previous draft did: the 'legally alive but operationally hollow' scenario. Even if August 2 holds as the binding deadline, multiple structural gaps make enforcement deeply uncertain regardless of whether the extension passes. First, only a minority of the 27 member states have designated competent authorities as of early 2026 — the exact figure varies by source and date, but multiple EU governance trackers confirm fewer than half have completed designation; we are sourcing this figure from the European AI Office's published readiness assessments and will update if the Commission releases more precise data. A regulator cannot initiate enforcement without a functioning competent authority to file it through. Second — and this is the point our previous draft got wrong — the absence of harmonized CEN/CENELEC standards does not legally prevent enforcement. The EU AI Act contains self-executing obligations; companies can demonstrate conformity through alternative assessment routes. But in practice, without harmonized standards, companies face genuine uncertainty about what compliance looks like, and regulators face genuine difficulty establishing a clear violation. This is compliance ambiguity, not a legal shield. It matters for enforcement probability but not in the categorical way we previously implied.

So what is our 35% actually measuring? To be precise: we are forecasting a 35% probability that August 2, 2026 remains the operative high-risk enforcement deadline — meaning no legislative extension has passed and been published in the Official Journal before that date, AND at least one competent authority has signaled it will apply the deadline as written rather than issue formal forbearance guidance. We are not forecasting that a flood of enforcement actions begins August 3. What would move us higher: a trilogue collapse — meaning formal breakdown of Digital Omnibus negotiations without a fallback mechanism — would push us toward 45-50%. What would move us lower: any credible provisional agreement between Parliament and Council before July, or a coordinated statement from multiple competent authorities signaling they will not initiate proceedings pending final legislative clarity.