10JUN

IRGC Navy writes its own Hormuz transit rulebook

3 min read

10:31UTC

Iran's Revolutionary Guard wrote its own transit rulebook for the Strait of Hormuz in the IRGC-aligned Farsi outlet Tabnak. The foreign ministry had no seat at the drafting.

← Back to Sovereignty law adopted; $40bn US chip buy Jump to analysis ↓

TechnologyDeveloping

Key takeaway

Iran's Revolutionary Guard wrote the Hormuz transit rules itself, and its own foreign ministry's clearances no longer hold.

On 17 April the IRGC Navy (Islamic Revolutionary Guard Corps Navy, Iran's parallel naval force) published a formal four-condition order for the Strait of Hormuz in the IRGC-aligned Farsi outlet Tabnak ¹. Non-military vessels may transit only by Iran-designated routes; military vessels are barred; every passage requires prior Guard Corps authorisation; the framework is tied to the Lebanon ceasefire holding.

The Tabnak publication lets Iran's military write over its diplomats in public. Two days later Foreign Minister Abbas Araghchi announced a civilian corridor opening, and the announcement lasted less than 24 hours. Despite the radio clearances Iran's own foreign ministry issued, the Guard Corps fired on the Indian-flagged Sanmar Herald and Jag Arnav on Saturday 18 April . A Sanmar Herald crew member was recorded on open channel saying Iran had cleared the vessel and was now firing on it anyway, which is the evidence the Tabnak order is load-bearing and the foreign ministry's clearances are not.

For shipowners routing hulls through the strait, the practical question is whose paper to obey. The rulebook the IRGC has now published is domestic Iranian doctrine with no signatory outside the Guard Corps. The 1968 Traffic Separation Scheme agreed between Iran, Oman and the IMO has governed Hormuz movement for 58 years, and Iran's own civilian foreign ministry is still a party to it. A counter-view from sympathetic commentators in Tehran is that the Tabnak order is a wartime clarification rather than a substitute for civilian law, and that a single ceasefire can fold it back. That reading is hard to sustain while the Guard Corps is firing on vessels the foreign ministry has cleared.

Deep Analysis

In plain English

Iran has two different armed forces: the regular military and the Islamic Revolutionary Guard Corps (IRGC), which is a separate, more ideologically driven force that reports to the Supreme Leader. On 17 April the IRGC Navy (its sea-going branch) published a set of four rules saying that no ship could cross the Strait of Hormuz without its personal permission, that military ships were banned entirely, and that the rules were tied to the Lebanon ceasefire holding. On 19 April Abbas Araghchi, Iran's Foreign Minister, separately announced the strait was open. Those two announcements directly contradict each other, and they came from two different parts of the same government. When Indian ships tried to follow the foreign minister's clearance, the IRGC fired on them anyway. The IRGC's written order, published two days earlier, turned out to be the one that governed the strait.

Deep Analysis

Root Causes

Iran never ratified the 1982 UN Convention on the Law of the Sea (UNCLOS), which grants transit passage rights through international straits. Tehran's domestic maritime law, updated in 2024, claims jurisdiction over 'hostile-linked vessels', a category broad enough to encompass any flag state that has sanctioned Iran.

The Tabnak four-condition order operationalises that domestic legal claim as a Guard Corps enforcement mechanism, creating a parallel legal architecture Iran can enforce without reference to international maritime law.

The IRGC Navy's institutional position since 2019 has been that Strait of Hormuz access is a tool of statecraft, not a neutral right. The Guard Corps has treated clearance authority as its own operational property through three rounds of tanker harassment. Araghchi's Friday corridor announcement conceded that institutional property without Guard Corps agreement, producing the split the Tabnak order makes legible.

What could happen next?

Precedent
The Tabnak order establishes IRGC written doctrine as the operative transit framework, creating a model for future enforcement that bypasses Iran's civilian foreign policy machinery.
Risk
Northwood planners drafting rules of engagement this week must write against a published adversary doctrine rather than a diplomatic silence, narrowing the range of enforceable coalition positions.

Source Landscape

This story draws on neutral-leaning sources

Primary parallel: In 1987-1988, Iran's Pasdaran naval units operated under Revolutionary Guard command authority that diverged from the regular navy's rules of engagement, producing the tanker attacks that triggered Operation Praying Mantis. The institutional structure (a parallel naval force writing its own doctrine separately from civilian foreign policy) is identical to what the Tabnak order documents in 2026.

Counter-parallel: The 2019 IRGC seizure of the Stena Impero was authorised through Iran's civilian judiciary as a legal response to Gibraltar detaining the Adrian Darya, demonstrating that Guard Corps naval action can run through, rather than against, civilian channels when Tehran chooses to coordinate. The Tabnak order's pre-dating of the Araghchi corridor by 48 hours suggests no such coordination this time.

Consensus view: The International Institute for Strategic Studies (IISS) reads the Tabnak publication as a deliberate command-authority claim: by writing the four-condition order before Araghchi's civilian corridor, the IRGC Navy established primacy in writing, then enforced it in fact when it fired on the Sanmar Herald . The Tabnak document is a retroactive paper trail for an authority the Guard Corps has exercised informally since 2019.

Counter-view: Former Iranian negotiator Hossein Mousavian, writing from Princeton's Program on Science and Global Security, argues the Araghchi-IRGC split is a structured bargaining posture: the civilian corridor creates international goodwill, the IRGC order provides a mechanism to revoke it, and the combination gives Tehran maximum leverage going into ceasefire renewal. Mousavian reads the Sanmar Herald firing as calibrated signalling, not institutional breakdown.

Key tension: Whether the Tabnak order reflects a genuine fracture in Iranian command authority or a choreographed good-cop/bad-cop mechanism that both factions have agreed on privately.

First Reported In

Update #74 · Two unsigned rulebooks collide at Hormuz

Tabnak· 20 Apr 2026

Read original →

Causes and effects

Caused by

Hormuz opens then closes in 24 hours

The IRGC Navy's 17 April Tabnak transit order provided the written doctrine that retroactively explained the IRGC firing on Indian tankers that had radio clearance (ID:2578).

Occurred 17 Apr 2026

Read story →

This Event

IRGC Navy writes its own Hormuz transit rulebook

Iran now has a civilian enforcement track and a parallel military one, and the military one is the document tankers hit first in open water. A clearance from Iran's foreign ministry buys nothing the Guard Corps has not signed off.

Led to

IRGC boards three ships inside Hormuz

The IRGC Tabnak four-condition transit order established the pattern of kinetic responses to verbal de-escalation, culminating in the 22 April seizures.

Occurred 22 Apr 2026

Read story →

Different Perspectives

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

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

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 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

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

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.