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

Rubio: US knew Israel would strike Iran

4 min read
10:31UTC

The secretary of state told Congress the US struck Iran because Israel's planned attack would trigger retaliation against American forces — his own words now form the core evidence in Congress's war powers challenge.

TechnologyDeveloping
Key takeaway

Rubio's statement is not a political gaffe but a legal admission that eliminates the administration's primary constitutional defence for the strikes.

Secretary of State Marco Rubio told congressional leaders on Monday that the United States knew Israel was going to strike Iran, knew that strike would provoke retaliation against American forces, and launched pre-emptive attacks to reduce the casualties the US would absorb from the consequences of Israel's operation. His words, reported by Al Jazeera and confirmed across multiple outlets: "We knew that there was going to be an Israeli action. We knew that that would precipitate an attack against American forces, and we knew that if we didn't pre-emptively go after them before they launched those attacks, we would suffer higher casualties."

The statement resolves a question that had been building since the campaign's first hours. Pentagon officials briefed congressional staff for ninety minutes on Saturday and reportedly produced no evidence for the White House's "imminent threat" claim . Senator Mark Warner, vice-chairman of the Senate Intelligence Committee, publicly stated he had seen no intelligence showing an immediate, imminent threat . Defence Secretary Pete Hegseth introduced a nuclear justification from the Pentagon podium on the same day . Rubio's admission goes further than any of these disclosures — it reframes the threat itself. The danger to American forces was not independent Iranian aggression but the foreseeable blowback from an Israeli operation Washington elected to join.

Under the War Powers Resolution of 1973, a president may commit forces without congressional authorisation only in response to an attack on the United States or its forces, or to address an imminent threat. Rubio described neither. He described a policy calculation: Israel would act, Iran would retaliate against US assets in the region, and pre-emptive American strikes would reduce the casualties Washington would absorb from its ally's war. That is alliance management — a strategic choice, not self-defence as the statute defines it. The distinction matters because it determines whether the president had lawful authority to launch the campaign without a congressional vote.

The war powers votes expected this week were always going to be symbolic — a presidential veto cannot be overridden with current margins. But Rubio has changed their evidentiary basis. Congress will now vote with The Administration's own account on record: the United States entered this war to manage the consequences of Israel's decision, not to counter an independent threat to American security. Six Americans are dead in 72 hoursthree in the initial retaliatory wave , a fourth at a tactical operations centre , and two more overnight. Netanyahu's contemporaneous declaration — "This Coalition of forces allows us to do what I have yearned to do for 40 years" — frames the American role from the Israeli side with equal directness. Between the two statements, the war's origins are described with unusual clarity by the principals themselves.

Deep Analysis

In plain English

US presidents are legally permitted to use military force without Congress's prior approval only in one circumstance: American forces face an immediate, unavoidable attack. Rubio has now publicly stated that the threat to US forces would only have existed because of a choice the US itself made — to join Israel's operation. That is the legal equivalent of saying 'we chose to walk into traffic, then swerved to avoid being hit.' The self-defence claim requires the threat to exist independently of your own decision-making. Congress now has the administration's own senior diplomat providing the evidence that the legal threshold was not met on the administration's own terms, while the campaign is still active.

Deep Analysis
Synthesis

The statement creates an inversion of the normal political dynamic: administrations typically face legal challenges only after operations end and documents are declassified years later. Here, the legal case against the administration's own war powers theory has been made by the Secretary of State in real time, while the campaign is active — removing the administration's ability to claim the legal question is unsettled and foreclosing the usual tactic of running out the clock on congressional scrutiny.

Root Causes

Four decades of presidential war-making through executive interpretation — from Reagan's Grenada to Clinton's Kosovo to both Bush administrations — eroded the expectation that presidents seek prior authorisation and atrophied Congress's institutional muscle for asserting it. The political cost of admissions like Rubio's has historically been near-zero because Congress has never successfully enforced the WPR against a sitting president; that normalisation is why the statement was made without apparent legal caution.

Escalation

The admission paradoxically constrains further escalation options: any expansion of operations — ground troops, additional strike packages — will face the same legal challenge with a compounding evidentiary record. Each new action taken under the same legal theory deepens the constitutional exposure rather than resetting it.

What could happen next?
  • Consequence

    The war powers vote this week is the first such vote where the administration's own senior diplomat has provided affirmative evidence against the legal threshold, creating a congressional record that will bind future legal challenges regardless of the vote's outcome.

    Immediate · Assessed
  • Risk

    A presidential veto of a War Powers Resolution — supported by the Secretary of State's own admission — would produce a constitutional standoff with no clear resolution mechanism, potentially paralysingstrategic decision-making during an active campaign.

    Short term · Suggested
  • Precedent

    Congressional failure to act on this admission would effectively remove the imminent-threat requirement from the War Powers Resolution as a practical constraint, leaving presidential war-making unconstrained by prior authorisation for all future administrations regardless of stated legal rationale.

    Long term · Assessed
First Reported In

Update #12 · Rubio rewrites war's legal case in Congress

Al Jazeera· 3 Mar 2026
Read original
Causes and effects
This Event
Rubio: US knew Israel would strike Iran
The administration's top diplomat has stated on the record that the legal threshold for presidential war-making — imminent threat to US forces — was not met independently but was instead a predictable consequence of an Israeli operation the US chose to support, transforming this week's congressional war powers vote from a political exercise into a constitutional confrontation armed with the administration's own testimony.
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.