Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
European Tech Sovereignty
10JUN

War-powers vote slips past its cliff

3 min read
10:31UTC

The House pushed its Iran war-powers vote to early June after the Memorial Day recess, leaving the 1 June statutory wind-down deadline to arrive before any floor vote can constrain the war.

TechnologyDeveloping
Key takeaway

The House delayed its war-powers vote past the 1 June deadline it was meant to enforce.

The House of Representatives confirmed on 24 May that its Iran war-powers vote would slip to the first week of June, after the Memorial Day recess 1. The reschedule follows Speaker Mike Johnson's cancellation of the vote on 21 May, hours before the chamber broke, as Republican absences left the resolution on the verge of passing . Sponsor Gregory Meeks must now wait until the House returns.

The War Powers Resolution is the 1973 law that requires a president to wind down undeclared hostilities within set deadlines absent congressional authorisation. Its 30-day wind-down cliff for the Iran campaign expires on Monday 1 June , the same day the House returns. The reschedule means the statutory deadline arrives first, with the vote that would have enforced it pushed past it.

That ordering matters because the cliff and the vote do different work. The 1 June deadline is a mechanical clock that fires whether or not the House acts; the floor vote is the political instrument that would convert the clock into a binding constraint on the war. By landing the recess between them, the calendar lets the deadline pass unenforced, leaving Trump's 86-day campaign to continue on the Article 2 doctrine the administration has asserted in place of any signed authorisation.

Deep Analysis

In plain English

In 1973, the US Congress passed a law called the War Powers Resolution (WPR). It says that if an American president sends forces into combat without a formal declaration of war, Congress must approve within 60 days or the president must begin pulling troops out within a further 30 days. The 60-day combat clock for the Iran war started in late February 2026 and expired in late April. The 30-day wind-down extension ends on 1 June 2026. The House of Representatives was going to vote before the Memorial Day break (25-26 May) on whether to order the president to stop the war under this law. But Republican leaders cancelled the vote because too many of their own members were going to vote against the president. They rescheduled the vote to the first week of June, meaning Congress will not vote until after the 1 June legal deadline has already passed. The Senate has already voted 50-47 to advance a similar measure. Whether any of this can actually stop a president who disagrees with it is a contested question: no war has ever been halted by the War Powers Resolution in the 53 years since it was enacted.

Deep Analysis
Root Causes

The House reschedule reflects a structural constraint specific to this Republican caucus. Speaker Mike Johnson cannot afford to lose a floor vote on a war powers question without triggering a motion to vacate his speakership, as happened to Kevin McCarthy in 2023. Johnson cancelled the vote rather than absorb a public defeat.

The post-holiday reschedule gives Republican members who were going to vote yes (motivated by constitutional principle, Massie and Paul's allies, or electoral vulnerability) a window to reverse their position in exchange for White House concessions that do not exist yet.

First Reported In

Update #106 · Trump says deal; OFAC says nothing

White House· 24 May 2026
Read original
Different Perspectives
European cloud and open-source industry
European cloud and open-source industry
European cloud providers gain a binding procurement mandate from CADA, confirmed by Gartner's $12.6bn sovereign-cloud figure for 2026. The $40bn Pax Silica commitment signals Brussels will not extend sovereignty discipline to the silicon layer, and the missing €350m Sovereign Tech Fund leaves open-source maintenance infrastructure unfunded beneath those same clouds.
United Kingdom
United Kingdom
Science Secretary Kendall's £1.1bn Hardware Plan on 8 June chose demand-side instruments, advancing £150m to British chip startups via the British Business Bank, where Brussels chose supply-side alliance membership. Britain joined Pax Silica before the EU and has no collective EU procurement leverage; the Hardware Plan is the bilateral answer to the same silicon gap.
United States
United States
Pax Silica, a State Department initiative launched in December 2025, secured EU membership the same afternoon Brussels adopted its cloud sovereignty law. Ambassador Puzder had named CADA a red line against the EU-US trade framework; the narrowed CADA scope and the $40bn chip commitment together represent the settlement Washington sought.
France
France
France was the only EU state to oppose Pax Silica accession at COREPER on 3 June, asking the Commission to clarify the Council's steering role inside the alliance. Paris backed CADA and hosts Mistral AI; a $40bn US-chip commitment contractually narrows the commercial space for the sovereign AI model that France is trying to scale.
European Commission
European Commission
Von der Leyen framed CADA on 3 June as keeping 'most of our market open to like-minded partners', and the Commission's EVP Virkkunen simultaneously required majority-European ownership for the €4.12bn AI Gigafactories call. Brussels is managing rather than resolving the silicon dependency by asserting regulatory control at the cloud layer while formalising the chip relationship through Pax Silica.
European Central Bank
European Central Bank
The ECB's digital euro pilot drew more than 50 PSP applications and is naming 10 to 30 participants in July, advancing on its own monetary mandate without requiring a Commission act. Its trajectory this week is the inverse of CAIDA's: the sovereignty instrument that restricts no US firm is the only one keeping its published calendar.