All entries

Signal Watch · Entry IRP_1 · Registered 29 March 2026

Aftermath transition. The booth is being negotiated, not closed. The cascade matured.

OpenHormuz cascade · aftermath transition

This entry has not been modified since 13 August 2026. Registration timestamp: 29 March 2026 · updated 7 May 2026 · updated 14 July 2026 · annotated 13 August 2026.

01

The signal

The MoU signed on 17 June, and Brent retraced toward pre-war levels through late June. Three weeks later, on 7 July, IRGC struck three tankers, and Trump declared the MoU over the following day at the NATO Turkey summit. The strait did not return to pre-crisis transit volumes across the interlude, and IMF PortWatch recorded 34 vessels a day on 5 July against an 88-vessel baseline. IRGC route enforcement against vessels off the Iran-approved corridor continued through the MoU window and did not pause when the deal was signed. The cascade that began on 28 February has now run through a full interlude-and-collapse arc, and the contracts, hedges, and shipping commitments written during the MoU window are entering renewal alongside the four months of the same that preceded them.

02

The read

The TIDES model from Complexity Science Hub Vienna mapped the cascade threshold before the strait crossed it. What TIDES showed is that a 56-day closure produces 2.5 times the logistics damage of a 28-day one, and the damage does not scale with time in a straight line: once the cascade crosses Day 28, port congestion compounds faster than shipping capacity can be re-routed to catch up, and the damage that follows is the compounding itself, not the closure. The Strait of Hormuz closed on 28 February, this entry issued on 7 May 2026 at Day 67, updated 25 May at Day 86, and updated again on 14 July at Day 136. The cascade crossed the TIDES threshold on 30 March at Day 28, and the second quarter ran inside the compounding regime.

Some things reverse when a deal signs and some do not. Spot freight rates reverse, war-risk insurance pricing reverses, the extra time Cape rerouting adds to voyages disappears when vessels stop taking the Cape, and fuel forwards reverse. What does not reverse are the contracts already re-priced against cascade-window baselines, the hedge books already rolled at cascade-window pricing, the capital investments already committed to cascade-window equipment, and the customer prices already changed at cascade-window terms. Maersk, Hapag-Lloyd, and CMA CGM ran emergency container surcharges of $1,500 to $3,500 through April, and those surcharges landed on customer contracts that mostly stay in effect through their own end dates. Iran's corridor ran at least twenty-six formal transits at $2 million per vessel since 13 March, with Western-flagged operators excluded throughout, and the fee schedule persists in legislated form whether or not the corridor is politically active in any given week.

The transmission runs in a specific sequence. The Hormuz closure on 28 February cut tanker traffic through the strait to about 2 percent of its baseline (IMF PortWatch data). Vessels rerouted around the Cape of Good Hope added roughly fourteen days to each leg and $750 to $1,200 in cost per shipping container, which is what carriers charged the emergency surcharges against. Port slots at the Northern European and Asian gateway ports formed backlogs as vessels arrived late and out of scheduled order, and the schedule unreliability cascaded through the gateway networks so that by 30 March, at Day 28, the cascade crossed the TIDES threshold and the compounding began. Two secondary cascades emerged on top of the primary one: Qatar helium force majeure hit semiconductor fabrication because about thirty percent of the world's helium is produced as a byproduct of Qatari LNG, and pharmaceutical active-ingredient supply chains compressed through the cold-chain logistics networks that share port capacity with everything else.

The 13 August annotation adds a constraint on this entry's central claim, from Banque de France Working Paper 1057 (Brockhaus, Hinz and Serfaty, August 2026). The paper models the toll regime this entry named, using AIS trajectories, port-call logs, and shipment-level customs data with a calibrated trade model, and two findings constrain the read. At a transit fee of plus thirty-five percent on exposed cargo, which the authors describe as the scale of fees under discussion since March 2026, Hormuz-transiting trade falls by roughly sixty percent and the toll sits close to the revenue-maximising region of its Laffer curve. A regime at its peak has no headroom. The incidence of the toll also falls on the Gulf rather than on its customers: Qatar minus 3.9 percent, Kuwait minus 2.7 percent, Iraq minus 2.5 percent, against Germany, France, and the Netherlands at roughly minus 0.01 percent each and Korea and India under minus 0.06 percent, and Iran, with an exposure of 0.95, levies most of the fee on its own trade and nets plus 1.5 percent while Oman, whose trade largely bypasses the strait, takes plus 12.2 percent as a near-pure transfer. What survives from this entry's original composition is the persistence claim in legislated form, the contract-calendar claim, and the pre-commitment cost differential for organisations that acted before Day 28. What the annotation constrains is the implication that a persisting toll transmits materially to downstream freight operators over the long run: the paper's long-run estimate is that importers substitute toward unaffected suppliers at low cost and the burden returns to Gulf producers, though the authors state explicitly that short-run importer costs could be larger where substitution is slower or constrained, which is the window this entry addresses. The read is not withdrawn, and its downstream-transmission implication now carries a named bound and a named source.

The 14 July update recorded what happened between the MoU signing and its collapse. The Islamabad Memorandum produced three weeks of Path 1 operating conditions, during which the governance-of-transit questions the MoU did not address, which authority controls corridor enforcement, whether differential pricing on Western-flagged vessels holds, and whether safe passage is conditional on the Iran-approved route, escalated inside the interlude rather than pausing during it. IRGC struck three tankers on 7 July, Trump declared the MoU over on 8 July at the NATO Turkey summit, and three rounds of US strikes hit more than three hundred targets between 7 and 12 July. Path 3 activated from inside Path 1's operating baseline, and the structure that emerged from the cascade is not temporary infrastructure to be dismantled once the situation stabilises. It is the operating regime the next four quarters run against, and no path resolution the corpus has substrate for reverses it inside that window.

03

Implications

If you are the COO running global freight operations, the pre-approval window for Cape routing on your remaining lanes closes at one to two weeks under normal conditions, and it tightens as the cascade progresses. Your bunker-fuel hedges for Q3 and Q4 2026 sit against a Dallas Fed three-quarter scenario at $132 a barrel, and locking them before Brent re-escalates through the forward curve is a different price than locking them after. Force-majeure documentation with timestamped supporting evidence is worth preparing now, before the next escalation removes the option to pre-position. The decision open at your operations review is whether to pre-approve capacity on the remaining lanes at roughly one times the current execution cost, or to chase capacity after the next flare-up at what has been running three times higher for the operators who did not act before Day 28. If you hold current lane routing and the cascade re-intensifies, your Q3 volumes arrive late through backlogged ports, the emergency capacity you buy in the compression window shows up on the P&L as freight cost you did not budget, and the delivery commitments you gave customers before the flare-up have to be re-negotiated under the compression conditions. The other side is quieter: if you pre-approve and Path 1 signs cleanly, the pre-approval cost sits on Q3 operations as a hedge that never had to fire, and the operations review absorbs the criticism of over-caution against a resolution that arrived on time.

If you are the CPO managing supplier risk, the war-risk insurance policies on your active supplier network need reviewing for explicit Persian Gulf and Hormuz coverage, and the 72-hour cancellation clauses in those policies are active right now. A cargo-composition read on your suppliers maps your liability exposure by Gulf-origin flow and Gulf-destination flow, and the secondary-cascade read surfaces the semiconductor and advanced-manufacturing suppliers holding Qatar-helium buffer stock as well as the generic-pharma suppliers whose active-ingredient production runs through the cold-chain networks the cascade has compressed. The decision open at your next supplier review is whether to re-price the risk premium against suppliers exposed to Gulf-origin or Gulf-destination flow now, or wait for a claim to trigger and re-price under the terms that follow. If you hold current supplier terms and the cascade escalates, a single supplier claim under the active 72-hour cancellation clauses pulls the coverage on the whole supplier network into re-underwriting inside a week, and the terms that come back sit at higher premiums and tighter coverage limits than the terms you can negotiate today with the cascade still not resolved. The other side: if you re-underwrite proactively and Path 1 signs, the premium adjustment stays in effect through the next policy year regardless, and the supplier network carries a higher risk cost against a resolution that would have made the adjustment unnecessary.

Across the three resolution paths, one operational shape holds for both the COO and CPO seats. Whether the deal signs on schedule, the compound continues through Q3 and Q4, or open conflict returns, the Iran toll regime persists in legislated form, and the strait reopens on your contract-calendar terms rather than on event-calendar terms. Organisations that pre-approved capacity and hedged in April have locked in a cost differential the rest of the market is now closing at six to eight times the pre-commitment cost. The decision open across both seats is whether to pre-position against the persistent-toll baseline this quarter or hold current position and pay the multiplier when the next flare-up compresses capacity. If you hold and Path 3 or Path 2 lands, the pre-approval cost you avoided in Q1 comes back as emergency-capacity cost in Q3 at higher magnitude and with worse P&L visibility, and the six-to-eight multiplier on that emergency capacity runs through your Q3 numbers before you can reprice customer contracts to absorb it. The Turkish Straits regime that persisted a century after its underlying crisis ended, which this entry named at Day 67 as a historical parallel, has empirical grounding in the July corridor-authority enforcement, and no path resolution the corpus has substrate for reverses the regime inside your Q3 and Q4 window.

04

The outcome

Status: Open. The horizon runs through Q3 and Q4 2026 and closes on the forward-market pricing of duration rather than on any single event resolution. Between the 29 March registration and now, the Islamabad Memorandum signed on 17 June and collapsed within three weeks after the 7 July IRGC strikes and Trump's declaration on 8 July, and the cascade completed a full interlude-and-collapse arc across the second quarter and into the third. The Banque de France annotation on 13 August 2026 added a constraint on the downstream-transmission implication, and the central claim, that the Iran toll regime persists in legislated form and the strait reopens on contract calendars rather than event calendars, has held across all three of Path 1, Path 2, and Path 3 as observed to date. The next update triggers on either a material configuration movement (further Iran corridor formalisation, a renewed political process on the MoU, or a substantial change in the enforcement pattern), the Q4 2026 close, or downstream freight-operator contract renewal data surfacing at scale, whichever arrives first.

05

How your Claude reads this

Your COO's Claude reads this position by querying BearingA over MCP. The read comes back as a structured position report against your specific configuration and horizon.

Position readCOO operations against Hormuz Day 136, Path 3 active, MoU collapsed 8 July
ConfigurationCompound cascade, aftermath transition, TIDES 2.5-times multiplier realised
Transmission pathHormuz closure cuts tanker traffic to about 2 percent of baseline, Cape rerouting adds 14 days per leg, port congestion follows at Northern European and Asian gateways, schedule unreliability cascades, and the cascade threshold crosses at Day 28
DirectionStructural, and the toll regime persists across all three resolution paths (Escalation, Compounding, De-escalation)
HorizonQ3 and Q4 2026, and the window closes on forward-market pricing of duration rather than on event resolution
Primary sourceIMF PortWatch, Lloyd's List Intelligence, TIDES model at Complexity Science Hub Vienna, and Maersk / Hapag-Lloyd / CMA CGM surcharge notices
Confidence boundsCentral claim survives all three resolution paths; magnitude sensitive to the Iran corridor formalisation timeline
Show the raw MCP invocationread_position(position="global_freight_operations", configuration="hormuz_cascade_path3", horizon="Q3_Q4_2026", altitude="COO_operations")
06

Primary sources

07

Cross-references

This entry was registered at 29 March 2026 · updated 7 May 2026 · updated 14 July 2026 · annotated 13 August 2026. It has been updated 0 times.

Every read BearingA has registered against active compound configurations, timestamped before the outcome window closes, drilled to primary source, revisited when the outcome resolves. No entries retracted; revisions annotated in-place with dated timestamps. The record is the epistemic commitment; individual read accuracy is the empirical question the record answers over time.