The EU AI Act Delay Is Politically Inevitable — But 'Inevitable' and 'Done' Are Different Things

Let's be direct about what drives the 35%. We're not betting on a political reversal — the 101-9 committee vote and the Commission's own authorship of the Digital Omnibus proposal make substantive opposition essentially nonexistent. What we're betting on is procedural execution risk: specifically, whether the trilogue can close, clear legal-linguistic review, and receive formal Parliament and Council votes before August 2. That's a tight legislative calendar for a process that has already required at least three political sessions. We estimate roughly 25 percentage points of our 35% come from that procedural timing risk alone, with the remaining ~10% covering low-probability scenarios — a court challenge from a member state or civil society group, a political reversal triggered by an AI incident, or a vote that technically passes but gets delayed in formal publication.

A word on precision that matters here: 'December 2027' as the new deadline requires qualification. Today's news cites DLA Piper sourcing that the Omnibus would move employment-related high-risk AI systems to December 2027. But the EU AI Act already contains tiered applicability — GPAI rules came into force August 2025, some high-risk categories embedded in regulated products (medical devices, critical infrastructure) have sector-specific extensions running to 2027-2029 under the base Act. We have not independently verified whether December 2027 is a uniform new date for all high-risk systems or a specific extension for a subset of categories. Our forecast is anchored to the August 2, 2026 deadline for the high-risk systems originally scoped to that date — if December 2027 applies only to employment-related subcategories, the forecast may still resolve YES for systems outside that scope. This is an unresolved precision issue we're flagging, not papering over.

On resolution conditions: we've been honest that the legal deadline surviving and the deadline being practically meaningful are two different things. Only 8 of 27 member states have designated competent authorities. CEN/CENELEC harmonized standards remain incomplete. Our forecast resolves YES if August 2, 2026 remains the binding statutory deadline without legislative modification — but we're adding a practical enforceability condition: YES resolution requires at least one national competent authority to have issued formal enforcement guidance specific to high-risk systems by that date. Without that condition, a YES resolution is a technicality, not a real outcome. We're building that into the linked forecast definition.

What would move us? A May 13 trilogue agreement that produces a formal text shifts us to approximately 15% — the residual covers formal vote timing risk. A May 13 failure without a new session scheduled before late June pushes us above 55%, because the calendar for legislative completion compresses beyond plausible. We also searched for organized opposition to the delay and found none credible — AI providers who invested in August 2026 compliance have not publicly organized against the Omnibus, and civil society concerns have centered on weakening enforcement ambition rather than opposing timeline extension. The 35% is procedural risk, not suppressed substantive opposition, and that distinction matters for how you read the number.