REPORT: What the Islamabad memorandum truly promised on June 17

Introduction: a text signed at the height of a war

A ceremony split between Versailles and Tehran

On June 17, 2026, two signatures sealed, on two different continents, the same fragile promise of peace. Donald Trump put his name to the Islamabad memorandum during a dinner at Versailles, alongside French President Emmanuel Macron on the sidelines of a G7 gathering, while Iranian President Massoud Pezeshkian signed it separately in Tehran. Pakistan and Qatar co-sponsored the text, lending it the weight of two regional mediators with direct stakes in the outcome.

This report goes back to the text itself, point by point, to measure the distance between what was promised on paper and what has actually happened on the ground since. That distance, as this reporting will show, has become the story itself.

Why this document deserves a full read, not a summary

Most coverage of the Islamabad memorandum reduced it to a single headline: a ceasefire. But the 14-point text contains far more, and far less, than that single word suggests. It contains detailed provisions on naval access, sanctions, reconstruction financing, and a negotiating calendar, while remaining strikingly silent on the two issues that mattered most in the long run: Iran's nuclear stockpile and its missile program.

Understanding those silences is just as important as understanding the commitments actually written down. This report treats both with equal seriousness.

A ceasefire that never names the missile program is not a peace deal, it's a temporary truce dressed up in diplomatic language. I read the Islamabad memorandum twice before writing this, and both silences jumped out exactly the same way.

Point one: an immediate ceasefire, including Lebanon

A ceasefire wider than the Iran-US front alone

The memorandum's first point calls for an immediate ceasefire covering not only direct hostilities between Iran and the United States, but also, explicitly, Lebanon, where tensions tied to Iranian-backed armed groups had flared in parallel with the broader regional escalation. Including Lebanon in the text acknowledged that this war never stayed confined to a single front.

This early recognition mattered diplomatically: it forced negotiators to treat the conflict as regional rather than bilateral from the very first page of the agreement, which shaped how every subsequent point was drafted.

What actually happened to this ceasefire

For a few weeks, the ceasefire largely held on the ground, interrupted mainly by isolated incidents rather than coordinated offensives. But by early July 2026, that calm had visibly eroded, culminating in the wave of attacks and strikes that would ultimately lead Trump himself to declare the ceasefire effectively over.

A ceasefire that survives for three weeks before collapsing under new provocations is not a failure of the text itself, but it is a clear signal that the underlying tensions the memorandum tried to freeze were never actually resolved.

Three weeks of relative calm is not peace, it's a pause bought on credit. I never believed this ceasefire would survive contact with Iran's own contradictions.

Point two: the naval blockade and the Hormuz clause

Thirty days to lift the blockade, sixty to guarantee free passage

The memorandum committed the United States to lifting its naval blockade of Iranian ports within 30 days of signature, while guaranteeing free and safe commercial passage through the Strait of Hormuz for a period of 60 days. This clause was meant to restore, at least temporarily, the flow of oil and goods that the war had disrupted for months.

On paper, this was one of the memorandum's clearest and most measurable commitments: a specific waterway, a specific timeframe, a specific guarantee. Few other points in the text offered this level of precision.

Violated before the sixty days even ran out

That precision made its violation all the more visible. On July 7, 2026, attacks struck the Qatari LNG carrier Al Rekayat and the Saudi supertanker Wedyan in waters covered by the free-passage guarantee, well before the 60-day window was set to expire. A third vessel was attacked the following day, and by July 11 to 12, the Revolutionary Guard declared the strait closed outright.

This sequence turns the Hormuz clause from a diplomatic success story into a textbook case of a commitment broken in slow motion, each new attack chipping away at what little credibility remained in the original guarantee.

Watching a 60-day guarantee collapse in under three weeks tells you everything about how seriously Tehran took its own signature. A promise broken this fast was never really a promise.

Point three: a $300 billion reconstruction fund with strings attached

Money conditional on a final deal that never arrived

Among its more ambitious provisions, the memorandum floated a $300 billion reconstruction fund intended to help rebuild infrastructure damaged during the war, explicitly conditioned on reaching a final, comprehensive agreement between Washington and Tehran. This was the carrot meant to balance the stick of continued sanctions pressure.

The scale of the figure alone signaled how much both sides had to gain from a durable settlement, and how much leverage the promise of that money was meant to exert on Iranian negotiators throughout the following weeks.

A fund that stayed entirely theoretical

Because the final comprehensive agreement never materialized, not a single dollar of this fund has moved. It remains, as of this report, a conditional promise attached to a negotiation that collapsed before reaching its intended destination. The fund's fate is a direct mirror of the broader memorandum's fate: real on paper, unrealized in practice.

This gap between announced sums and delivered outcomes is not new in Middle East diplomacy, but it remains a useful reminder that headline figures in ceasefire agreements often function more as incentives than as guarantees.

Three hundred billion dollars that never left the page isn't generosity, it's a bargaining chip that expired the moment Iran chose escalation over patience.

Point four: sanctions relief granted, then partly reversed

A rapid concession on June 21

Just four days after the signing, on June 21, 2026, the United States granted a first round of sanctions relief tied to the memorandum's implementation, easing restrictions that had squeezed Iranian oil exports and financial transactions for months. This rapid move was meant to demonstrate good faith and build momentum for the harder negotiations to come.

For a brief window, this looked like the fastest tangible benefit either side had delivered under the new framework, a rare piece of good news in an otherwise grinding conflict.

Reimposed within weeks

By mid-July, following the tanker attacks and the closure of the Strait of Hormuz, the U.S. Treasury Department reimposed sanctions on Iranian oil exports, along with new measures targeting the Revolutionary Guard's financial network and figures close to Mojtaba Khamenei. The concession granted on June 21 had a shelf life of barely three weeks.

This reversal illustrates, with unusual clarity, how quickly a de-escalation framework can unravel when one party continues military provocations in the middle of the very negotiations meant to end them.

Sanctions relief lasted less than a month before Iran's own actions forced Washington to reverse course. That is not Western impatience, that is Tehran testing a rope it knew could snap back.

Point five: total silence on the nuclear file

No cap, no dilution, no relocation

Perhaps the memorandum's most consequential feature is what it does not say. The text includes no binding cap, no dilution requirement, and no relocation plan for Iran's stockpile of roughly 440 kilograms of uranium enriched to 60%, a level far above civilian needs and dangerously close to weapons-grade material. Both sides merely commit to negotiating a management mechanism for this stockpile at some later stage.

This is not an oversight buried in fine print; it is a structural gap at the center of the entire agreement, one that leaves the single most dangerous element of the standoff essentially untouched by the ceasefire itself.

A status-quo clause that became a loophole

The memorandum's status-quo language, meant to freeze positions during the negotiating window, includes no explicit freeze on reconstruction activity at nuclear-linked sites. That omission is precisely the loophole that satellite imagery released in mid-July would later expose, showing rebuilding activity at sites like Pickaxe Mountain and Parchin months after they were struck.

A status-quo clause this porous does not freeze anything meaningful; it simply legalizes whatever ambiguity already existed on the ground.

A peace text that forgets to freeze construction at nuclear sites isn't a technical oversight, it's the exact hole a regime like Iran's was always going to slip through.

Point six: sixty days to negotiate, a deadline already passed

The Bürgenstock track and its mediators

The memorandum set a 60-day window for substantive negotiations, to be conducted through talks in Bürgenstock, Switzerland, which began on June 21, 2026, under the mediation of Pakistan and Qatar. This track was meant to translate the memorandum's broad principles into a detailed, binding final agreement covering everything the initial text left vague.

Choosing a neutral Swiss venue and pairing it with regional mediators reflected an attempt to give the talks both international legitimacy and local credibility, a combination diplomats hoped would keep both Washington and Tehran at the table.

A deadline that came and went without a deal

Sixty days from June 21 places the deadline around July 8, 2026, a date that had already passed by the time the tanker attacks and the full closure of the Strait of Hormuz dominated headlines. No final agreement emerged from the Bürgenstock track before that deadline, leaving the entire nuclear and missile files exactly where the original memorandum had left them: unresolved.

A negotiating window that closes without producing the deal it was designed to produce is not a neutral outcome; it is a diplomatic failure with direct consequences for everything that followed in the days after.

Missing your own deadline while the strait you promised to keep open is being shut down isn't bad luck, it's a negotiation that never had a real chance once one side kept escalating.

Point seven: the missile program, entirely absent from the text

A file the memorandum never opens

Nowhere in the 14 points does the memorandum address Iran's ballistic and cruise missile program, despite that program being directly responsible for the strikes on five Gulf countries that would later shatter the ceasefire. This silence stands alongside the nuclear-file silence as the memorandum's second structural blind spot.

Leaving an entire weapons category outside any negotiating framework meant that Iran retained full freedom to use missiles as leverage throughout the ceasefire period, which is precisely what happened when tensions escalated in early July.

Why this omission mattered so much in practice

When Iran fired missiles and deployed drones against Jordan, Kuwait, Qatar, and Bahrain between July 9 and 10, it violated no explicit clause of the memorandum, because no clause governed missiles in the first place. This legal vacuum let Tehran escalate militarily while technically remaining, on this specific point, outside the letter of the agreement it had signed.

A ceasefire text that regulates ships but not missiles leaves its authors negotiating half a war, and the other half came due exactly when it was least convenient for the process.

Forgetting to mention missiles in a ceasefire with Iran is like forgetting to mention water in a drought agreement. This omission wasn't a footnote, it was the whole story waiting to happen.

The funeral pause that froze implementation

Six days that stopped the diplomatic clock

The death of Supreme Leader Ali Khamenei, killed in the American-Israeli strikes of February 2026, triggered state funerals spread across Tehran, Qom, and Mashhad, drawing, according to Iranian state media estimates, between 41 and 43 million mourners. Implementation talks tied to the Islamabad memorandum paused for the full duration of this mourning period.

This pause was not written into the original text; it was an unplanned interruption that nonetheless shaped how much time remained, in practice, for the 60-day Bürgenstock window to produce results before its own deadline expired.

Ghalibaf's remarks from the funeral podium

During the funeral proceedings, senior Iranian official Mohammad Bagher Ghalibaf delivered remarks from the funeral podium that were widely read as signaling continued defiance toward Western pressure, even as pragmatists within the regime continued negotiating in parallel. This split messaging, mourning and defiance delivered from the same stage, captured the internal fracture running through Iran's leadership during this period.

A regime that buries its supreme leader while its officials use the funeral itself as a platform for political signaling is not a regime speaking with one voice, and that lack of unity would resurface again and again throughout this report.

Using a funeral podium to signal defiance while your diplomats negotiate down the hall tells you everything about which faction actually controls Iran's foreign policy right now.

The first violation: tanker attacks on July 7 and 8

Two ships hit in international waters

On July 7, 2026, the Qatari LNG carrier Al Rekayat and the Saudi supertanker Wedyan were struck in waters the memorandum had explicitly guaranteed as safe for commercial passage. A third vessel was attacked the following day, confirming that the first incident was not an isolated accident but the opening move of a deliberate campaign.

These attacks marked the memorandum's first documented, unambiguous violation, striking directly at the one clause negotiators had considered among the text's most concrete and measurable commitments.

From isolated incident to full closure

What began as attacks on two commercial vessels escalated, within days, into the outright closure of the Strait of Hormuz by the Revolutionary Guard on July 11 to 12, following a third wave of American strikes on roughly 140 Iranian targets. The progression from tanker attack to full strait closure took less than a week.

This rapid escalation shows how quickly a single violated clause can cascade into a wholesale collapse of the broader framework, especially when neither side shows willingness to absorb the first provocation without responding in kind.

Two tankers hit in a week became a closed strait within days. I watched this unravel in close to real time, and at no point did it look like anything other than Iran choosing escalation over the deal it signed.

Trump declares the ceasefire over

A statement that registers the collapse

Facing the tanker attacks and the closure of the Strait of Hormuz, Donald Trump declared this week that he considers the ceasefire over. This is not a rhetorical flourish; it is the highest-level American acknowledgment that the framework negotiated in Islamabad weeks earlier has, at least temporarily, ceased to function as intended.

This declaration also opened the door to the intensified American response already underway, including the strikes on roughly 140 targets that followed almost immediately.

What this means for the Bürgenstock track

With the ceasefire declared over by the American side and the 60-day Bürgenstock negotiating window already expired without a final deal, the entire diplomatic architecture built around the Islamabad memorandum now sits in a kind of suspended animation, neither formally dead nor functioning as originally designed.

Whether this framework can be revived, or whether an entirely new negotiating track will need to replace it, remains one of the most consequential open questions facing Washington, Tehran, and every regional actor caught in between.

Trump was right to call this ceasefire over once Iran itself had already broken it in practice. Pretending otherwise would have only rewarded bad faith with more time to exploit.

Iran strikes five Gulf countries in 48 hours, then denies it was the aggressor

A regional barrage that widened the war

Between July 9 and 10, 2026, Iran fired missiles and deployed drones against the Al-Azraq air base in Jordan, along with targets in Kuwait, Qatar, and Bahrain, hitting a Patriot air-defense system, a munitions depot, a radar site, and refueling platforms at the port of Duqm in Oman. The Revolutionary Guard also claimed strikes on Jordan's Prince Hassan air base.

This barrage against five separate jurisdictions within 48 hours transformed what had been, on paper, a bilateral US-Iran ceasefire into a genuinely regional crisis touching countries that had no direct stake in the original dispute.

Al Udeid, the strike that hit a co-sponsor directly

Among the targets claimed by the Revolutionary Guard was the Al Udeid air base in Qatar, one of the two countries that had co-sponsored the Islamabad memorandum itself. Striking the territory of a mediator nation added a layer of diplomatic irony that was not lost on regional observers.

A regime that bombs the host country of its own mediation process sends an unambiguous signal about how much weight it actually places on the diplomatic channels it agreed to use.

Striking the very country that co-sponsored your peace memorandum isn't an accident of war, it's a message about how little that memorandum ever meant to Tehran.

The position of Pakistan and Qatar, mediators under pressure

Caught between their own sponsorship and the fallout

Having co-sponsored the Islamabad memorandum, Pakistan and Qatar now find themselves managing the diplomatic fallout of an agreement collapsing in real time, including, in Qatar's case, being directly struck by one of the two parties it had helped bring to the table. Their continued willingness to host talks in Bürgenstock and elsewhere reflects genuine investment in salvaging the process, even as events undercut it.

This position is uncomfortable but not without leverage: both countries retain channels of communication with Tehran that Western capitals lack, making their continued mediation valuable even after the memorandum's practical collapse.

Why their continued role still matters

Despite the setbacks, abandoning Pakistani and Qatari mediation now would likely remove one of the few remaining bridges between Washington and Tehran at a moment when direct communication has become nearly impossible. Their bruised but intact position as intermediaries may end up being one of the only usable assets left from the entire Islamabad framework.

Any future negotiating track will likely need to build on, rather than replace, the channels these two mediators have already established, however damaged those channels currently appear.

Qatar getting struck while still trying to mediate this conflict deserves more sympathy than it has received. Being a peace broker in this region has never been a safe job, and this episode proves it again.

Presenting closure as pure self-defense

Iranian outlets including Tasnim and IRNA framed the closure of the Strait of Hormuz as a defensive response to what they described as American interference in the region, largely omitting any mention of the tanker attacks and missile strikes that Tehran itself had launched in the days prior. This selective narrative left out the very violations that triggered the American response.

A framing this incomplete does not reflect a misunderstanding of the sequence of events; it reflects a deliberate choice to present only the half of the story that casts Iran as the aggrieved party rather than the initial aggressor.

Why this framing does not survive the documented timeline

The documented timeline established in this report, tanker attacks on July 7 and 8, missile strikes on five countries on July 9 and 10, followed by the American response and the strait's closure on July 11 and 12, does not support the defensive narrative Iranian state media has offered. The sequence shows Iranian escalation preceding, not following, the American strikes that triggered the closure.

Reporting accurately on this file means naming that sequence explicitly, rather than repeating a framing that the public record itself contradicts.

Calling this closure self-defense while skipping the tanker attacks you launched first isn't spin, it's a direct contradiction of your own government's timeline. I won't repeat a narrative the facts themselves disprove.

What Kyiv reads into this collapse

A familiar pattern of promises and provocations

In Kyiv, analysts following the Islamabad memorandum's collapse see an uncomfortably familiar pattern: an agreement signed with real fanfare, followed by a slow erosion through incremental violations that never quite trigger a full renegotiation until the damage is already done. The parallel with Vladimir Putin's repeated ceasefire violations in Ukraine since 2022 is impossible to ignore.

This comparison is not a claim that the two conflicts are identical, but a recognition that authoritarian negotiating partners often share the same playbook: sign, delay, violate incrementally, and count on Western diplomatic fatigue to absorb the cost.

The lesson for future frameworks

If there is one lesson the Islamabad memorandum's collapse offers Western diplomacy more broadly, it is that vague provisions on the most dangerous files, nuclear stockpiles, missile programs, are not neutral gaps; they are the exact seams that authoritarian regimes will pull apart first. Future agreements, whether with Iran or in the context of Ukraine, should close those seams explicitly rather than deferring them to a later negotiating round that may never arrive.

Ignoring this lesson risks repeating, indefinitely, the same cycle of hopeful signature followed by disappointing collapse that has now played out twice within a matter of months.

What happened to the Islamabad memorandum is what happens every time the West leaves the hardest questions for later. Ukraine has been paying that same price for years, and Iran just proved the lesson still hasn't been learned.

Conclusion: a memorandum measured against its own promises

What the text delivered, and what it never touched

Measured against its own 14 points, the Islamabad memorandum delivered a short-lived ceasefire, a brief round of sanctions relief, and a negotiating track that ultimately missed its own deadline. It never delivered a resolution on Iran's nuclear stockpile, never addressed the missile program at all, and left its naval-passage guarantee in ruins within weeks of signature.

This is not a balanced scorecard between the diplomatic effort and the outcomes achieved; it is a document whose most consequential silences ended up mattering far more than its most detailed provisions.

What comes next for this diplomatic track

Whether the Bürgenstock talks, the Doha channel, or an entirely new framework eventually replaces what the Islamabad memorandum could not sustain, any future text will need to name explicitly what this one left vague: the nuclear stockpile, the missile program, and a verification mechanism strong enough to survive the next funeral, the next tanker attack, and the next provocation.

Until that happens, every ceasefire signed with Tehran will carry the same structural weakness this report has documented in detail: real commitments on secondary issues, and silence on the ones that matter most.

Signed Maxime Marquette, columnist

Columnist's transparency note

A report built on the memorandum's own text and public statements

This report is based on the publicly available text and reporting concerning the Islamabad memorandum, cross-referenced with subsequent statements from American, Iranian, and regional officials. The italicized passages reflect the author's personal opinions, clearly identified as such, and should not be confused with the factual reconstruction of events, which rests on dated, verifiable sources.

Limits and uncertainties of this report

Some elements, notably the full internal deliberations behind Iran's decision-making during this period and the precise chain of command behind the missile strikes on five Gulf countries, remain outside the scope of publicly verifiable sources and should be read with appropriate caution. The author commits to correcting any factual error brought to their attention.

Sources

Primary sources

Times of Israel, regional coverage of the Iran-Israel-US crisis — July 2026

Foreign Policy, geopolitical analyses on Iran and the Gulf — July 2026

Al Jazeera, live blog on the closure of the Strait of Hormuz — July 12, 2026

Secondary sources

Wikipedia, full text and context of the Islamabad memorandum — June 2026

CNN, American strikes on 140 targets after attack on a vessel — July 11, 2026

JNS, draft outline of the US-Iran ceasefire and nuclear provisions — 2026

SpecialEurasia, analysis of the Bürgenstock negotiations — June 22, 2026