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

Israel hits Iran after Trump said no

3 min read
10:31UTC

Trump publicly urged Netanyahu not to retaliate; on Monday 8 June the IDF struck the Mahshahr petrochemical complex and missile sites inside Iran regardless.

TechnologyDeveloping
Key takeaway

Trump asked Israel not to strike Iran; Israel struck the next day, exposing his leverage as rhetorical.

President Donald Trump publicly urged Benjamin Netanyahu not to hit back at Iran, saying he would call him and "tell him not to strike back" 1. On Monday 8 June the IDF (Israel Defense Forces) struck military targets inside Iran regardless: the Mahshahr Petrochemical Complex in Khuzestan province and surface-to-surface missile launch sites, with blasts reported in Tehran, Tabriz and Isfahan 2. Iranian officials and Israel's Magen David Adom reported minimal-to-no casualties on either side, preliminary 3.

Netanyahu reportedly agreed to the request, then struck anyway. For 100 days the war's central gap was passive, with no US-Iran instrument on paper while the fighting ran on ; on Monday it turned active. Trump asked his closest ally, in public, to hold fire, and the answer on the ground was the Mahshahr strike.

Two readings hold at once. One is plain defiance: Israel will not let Tehran fix the terms of the exchange, and Trump cannot make it. The other is choreography, a good-cop, bad-cop split that lets Israel apply the kinetic pressure Trump keeps off his own diplomatic ledger. No signed US instrument exists to prove Washington controls the kinetic track, so the burden of demonstrating coordination sits with the White House.

Either way, the strike adds a fresh complication to the negotiating file. Rezaei's $24bn precondition was already unresolved; a unilateral Israeli strike against Trump's stated wish now sits beside it as a US-Israel alignment gap.

Deep Analysis

In plain English

Israel's military struck inside Iran on 8 June, hitting a large petrochemical factory in Khuzestan province (south-western Iran) and sites used to launch surface-to-surface missiles. Explosions were also heard in Tehran, Tabriz and Isfahan. US President Trump had publicly asked Israel's Prime Minister Netanyahu not to strike back after Iran's missile attack. Israel struck anyway. Mahshahr is one of Iran's biggest chemical production hubs. Israel hit the same complex in April 2026. Netanyahu reportedly told Trump he had agreed not to strike, then authorised the attack. No verified casualties were reported in the early hours, though that may change.

Deep Analysis
Root Causes

Israel's coalition politics under Netanyahu require maintaining offensive operational tempo: Ben Gvir and Smotrich's continued participation in government is conditioned on rejecting any ceasefire that does not meet maximalist terms.

Netanyahu's government falls if he accepts US-brokered de-escalation without a full agreement. Compliance with Trump's restraint requests is blocked by Israeli coalition arithmetic, not by strategic disagreement about Iran's threat level.

What could happen next?
  • Consequence

    Trump's public restraint request failing within 24 hours removes his ability to use 'I can control Israel' as a credible bargaining chip with Tehran in ongoing nuclear negotiations.

  • Risk

    A second Mahshahr strike compounds the April damage to Iran's domestic fuel supply, increasing civilian pressure that could either force concessions or harden hardliner resistance to any deal.

First Reported In

Update #121 · Trump said don't strike; Israel struck Iran

Jerusalem Post· 8 Jun 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.