17MAY

Rosatom evacuation done; 24 volunteers remain

3 min read

14:28UTC

Lowdown Bureau / Infrastructure. Russian technicians are out of Bushehr; Peskov is still publicly offering the custody mechanism the evacuation has gutted.

← Back to Brussels' 27 May package, two days before G7 Jump to analysis ↓

TechnologyDeveloping

Key takeaway

The uranium custody offer is still rhetoric; the technicians who would execute it are on an evacuation flight.

Rosatom CEO Alexei Likhachev confirmed on Monday through TASS that the evacuation of Russian personnel from the Bushehr Nuclear Power Plant is complete. Twenty-four volunteers remain on site 'to maintain the operability of nuclear power units'. Likhachev disclosed the fuel inventory: 72 metric tonnes of fresh nuclear fuel and 210 metric tonnes of spent fuel. The main evacuation wave of 198 staff moved toward the Armenian-Iranian border after a projectile strike near the facility killed a security guard .

Kremlin spokesman Dmitry Peskov is still publicly advancing the Rosatom uranium-custody offer, the three-option proposal Moscow sketched in March through which Russia would take transfer of Iran's stockpile. The mechanism requires Russian technicians on Iranian soil handling Iranian material under a bilateral transfer architecture. Those technicians are now in Russia. The offer and the capacity to deliver on the offer are operating on different continents.

For the nuclear track, Moscow's custody offer has been the fallback ever since the Majlis voted 221-0 to suspend all cooperation with the International Atomic Energy Agency (IAEA), the UN nuclear watchdog. Rafael Grossi warned last week that any agreement without inspector access would be 'an illusion' . ANS monitoring this month confirmed Fordow remains inoperable since the June 2025 Midnight Hammer strikes . Bushehr is now the only large pre-existing fuel stockpile inside Iran, and 282 tonnes of material sit under two dozen people, no inspectors, and no Russian specialists.

Pakistan's four-country monitoring framework is the only remaining 2026 track with movement behind it. A monitoring architecture that depends on Russian technicians Moscow has withdrawn, Iranian cooperation the Majlis has revoked, and inspectors the IAEA cannot place on the ground is not a monitoring architecture. Peskov's continued public framing of the custody offer functions as rhetorical leverage, not as an operational mechanism. Whether Moscow reverses the evacuation in exchange for concessions, or lets the gap widen, is the most consequential nuclear-track decision of the next fortnight.

Deep Analysis

In plain English

The US government keeps an official website (state.gov) where it publishes formal agreements with other countries. On 20 April, the site published the text of the ceasefire between Israel and Lebanon; a proper document listing both countries as parties and the United States as broker. No equivalent Iran ceasefire document has appeared on state.gov, whitehouse.gov, or the Federal Register across 52 days of conflict. No ceasefire text has ever appeared on state.gov, the White House website, or in the government's official Federal Register in 52 days of conflict. The ceasefire between the US and Iran exists only as statements by unnamed officials quoted in news reports. This matters because a document that does not officially exist cannot be officially violated, extended, or enforced. When the ceasefire expiry passes on Wednesday with no signed document, there is nothing to lapse legally.

Deep Analysis

Root Causes

The Iran ceasefire instrument gap reflects a structural choice rooted in US executive branch incentives. A published state.gov ceasefire text requires an authorised signatory, a defined scope, and a named ceasefire area; each element creates Congressional and legal accountability that the administration has consistently avoided on the Iran file across 52 days.

The Lebanon text was published because both Israel and Lebanon are recognised government parties capable of executing a named bilateral agreement. Iran's status as a designated state sponsor of terrorism creates legal constraints on US signatories that do not apply to the Lebanon parties.

The 0 vs 1 instrument asymmetry between Iran and Lebanon, visible on the same day, exposes the Iran gap as a deliberate administrative choice rather than a capacity failure. The State Department legal team that drafted the Lebanon text operates under the same Secretary of State as the Iran portfolio; the difference is political will, not bureaucratic capacity.

What could happen next?

Precedent
The Lebanon text's state.gov publication demonstrates the US government's capacity to produce a formal ceasefire instrument within the same 52-day window; making the Iran instrument gap a deliberate choice rather than an administrative oversight.
Risk
Without a published Iran ceasefire instrument, any resumption of hostilities after Wednesday cannot be formally characterised as a ceasefire violation; removing a legal deterrent that a signed instrument would provide.

Source Landscape

This story draws on centre-left-leaning sources from Netherlands

Netherlands

Primary parallel: The 1994 Agreed Framework between the United States and North Korea was published on state.gov and signed by both parties. It collapsed in 2002 not because it lacked legal form, but because neither side implemented its obligations. The lesson: publication on state.gov confers legal form but not compliance. The Iran ceasefire's absence from state.gov means it lacks even legal form.

Counter-parallel: The 1988 Iran-Iraq War ceasefire operated under UN Security Council Resolution 598, not a bilateral US-brokered document. Iran and Iraq did not sign a document with the United States; they accepted a UN resolution. The current US-Iran ceasefire has no equivalent multilateral framework, making the Lebanon text (a US-brokered bilateral) the closest structural parallel; and its absence for Iran the most visible gap.

Consensus view: Chatham House's Sanam Vakil identifies the state.gov Lebanon text as the first US-brokered ceasefire document of the war to pass the legal publication test: a named parties clause, a brokering-state declaration, and a formal state.gov URL. The Iran ceasefire, by contrast, has never appeared on state.gov, whitehouse.gov, or the Federal Register; meaning it exists only as attributed quotes from unnamed officials.

Counter-view: The University of Tehran's political faculty (Mostafa Dolatyar) argues the absence of a formal Iran instrument reflects rational interest on both sides: a published ceasefire text creates legally actionable obligations that both Washington and Tehran prefer to avoid, since either side breaking a named agreement carries diplomatic costs that breaking an undocumented arrangement does not.

Key tension: Whether the Lebanon text's publication inadvertently exposed the Iran ceasefire's legal vacuum, creating pressure for a comparable Iran instrument; or whether the two tracks are structurally incomparable because the Lebanon parties (sovereign governments) are capable of signing a state.gov-publishable document in a way Iran currently is not.

First Reported In

Update #75 · Ceasefire ends in the water, a day early

Moscow Times· 21 Apr 2026

Read original →

Causes and effects

Caused by

Rosatom walks 180 staff out of Bushehr

Likhachev's 20 April confirmation of complete evacuation advanced the partial 16 April evacuation, adding 24 confirmed remaining volunteers and disclosing the full 282-tonne fuel inventory.

Occurred 16 Apr 2026

Read story →

Grossi: any deal without inspectors is illusion

Grossi's warning that any deal without inspector access would be an illusion was compounded by Rosatom's confirmed evacuation, removing the last non-Iranian technical presence at Bushehr.

Occurred 18 Apr 2026

Read story →

This Event

Rosatom evacuation done; 24 volunteers remain

282 tonnes of fissile and radioactive material at Bushehr now sit under a 24-person skeleton crew, with no IAEA inspectors and no Russian technicians to execute Moscow's standing custody offer.

Different Perspectives

OpenForum Europe / open-source community

The EUR 350m Sovereign Tech Fund has no Commission host, no budget line, and no commissioner's name attached six weeks after the April conference, while Germany is already paying maintainers to staff international standards bodies. The CRA open-source guidance resolves contributor liability but leaves the financial-donations grey area open with the 11 September reporting clock running.

ASML / Christophe Fouquet

ASML's Q2 guidance miss of roughly EUR 300m below consensus reflects DUV revenue compression set by US export controls, not European policy. Fouquet said 2026 guidance accommodates potential outcomes of ongoing US-China trade discussions; a bipartisan US bill to tighten DUV sales further would accelerate the cross-subsidy thinning Chips Act II's equity authority is designed to address.

Anne Le Henanff / French G7 Presidency

Le Henanff chairs the 29 May Bercy ministerial two days after Brussels adopts the Tech Sovereignty Package, making the G7 communique the first international read of the Omnibus enforcement split and CAIDA's scope. France's Cloud au Centre doctrine is already operational via the Scaleway Health Data Hub contract.

German federal government

Berlin operationalises sovereignty through procurement mandates (the ODF requirement and the Sovereign Tech Standards programme) rather than waiting for Commission legislation. The Bundeskartellamt has still not received the Cohere-Aleph Alpha merger filing, leaving Germany's flagship AI champion in structural limbo six weeks after the deal resolved.

US Trade Representative

The USTR Section 301 investigation into EU digital rules closes with a 24 July 2026 final determination. CAIDA's public-sector cloud restriction sits within the criteria that triggered the 2020 Section 301 action against France's digital services tax, and the US has not signalled whether the Thales-Google S3NS arrangement resolves CLOUD Act jurisdiction concerns.

CISPE / Valentina Mingorance

CISPE shipped its own pass-fail sovereignty badge in April to establish an industry-auditable floor the Commission could adopt. Whether CAIDA inherits the CISPE binary or the multi-tier SEAL approach will determine whether certification is enforceable by public contracting authorities or requires Commission discretion.