Worked case · Chapter 9, Networks, Dependence, and Resilience · p. 360 · sources checked 10 November 2026
Shipping through the Strait of Hormuz under threat
what loss can protection guarantee, what does predictability cost, and should ships be gathered into fewer windows or spread over more?
The network
- Protector → Transit windows acts escort units per window, randomised
- Threat → Transit windows acts strike units per window
- Protector → Threat commits may publish the mixture or a fixed schedule
- Transit windows → Shipowners and insurers pays expected loss
The mapping
The six fields of the model card, as the book fills them in for this situation.
| Field | In the case |
|---|---|
| 1 Decision-makers | a protector — the naval missions and the guidance they give, treated as one — assigning escort units to transit windows; a threat assigning strike units, used as a worst case and not as a description of any party; shipowners and insurers stand outside the game and read its value |
| 2 Time | one period, a day of transits; days are not linked, and neither repairs nor the evolution of the threat are modelled |
| 3 Information | the traffic plan and both budgets are known; neither side sees the other's realised allocation; in a variant the escorts' positions are visible before a strike |
| 4 Commitment | the protector may publish its policy (the mixture) or a fixed schedule; the threat commits to nothing |
| 5 Payoffs | ships that pass, ties to the protector; for an insurer, the loss per transit times the fraction of hull value lost when a ship is hit gives the break-even additional premium |
| 6 Strategies | randomised integer allocations of escort and strike units to the windows |
What the mathematics licenses.
Five statements about the model; the mapping to the strait is a reconstruction R, and no statement estimates any real loss, premium or escort requirement.
- A guarantee needs no reading of intentions. The value bounds the loss against every allocation of the threat's units, whatever their purpose, as long as the threat can bring no more than units to bear. In the base case the protector can hold the expected loss to of six ships, and a threat of that strength can impose ; a pooled cover priced from the guarantee breaks even at a per-transit rate of . What the bound needs is capability — how many units can be brought to one window — not intent D [Proposition 9.16 (p. 381)(a)]; how capability maps to “units” is a reconstruction R.
- What costs is a visible draw, not a published policy. A fixed schedule loses ships against its best reply, and so does a rotating schedule whose realised assignment the threat sees before striking: the break-even rate rises by half, from to . Publishing the mixture itself costs nothing in this zero-sum game D [Proposition 9.15 (p. 380)(b), Proposition 9.16 (p. 381)(a)]. This is Chapter 2's observability branch (Proposition 2.10 (p. 97)) and Chapter 6's revealed inspection (Proposition 6.4 (p. 254)) in the setting of escorts. In the record, the advisories' guidance on AIS transmission and the announcements of naval presence bear on this field of the card, field 3; how much they reveal of a day's allocation is an empirical question R.
- Unpredictability is worth something only against the middle of the three threats compared. With one strike unit the base plan loses nothing even when it is predictable; with three it loses whether it is predictable or not; only with two units is randomising worth of a ship D [Proposition 9.16 (p. 381)(a)]. The comparison is these three budgets, not a rule in the threat's strength: a rotation worth keeping against one level of threat may be worth nothing against another.
- Convoy or disperse: the ranking reverses with the escorts. Escorts lose nothing if and only if D [Proposition 9.15 (p. 380)(a)]. Below that threshold the effect of spreading the six ships over more windows depends on where the escort budget stands: with three escorts more windows lower the loss ( in two windows, in three, in six), but not below every budget. With four escorts the two-window plan is safe while three and six windows each lose ; with five the order is the reverse of the order with three: , , (tab:net-hormuz,fig:net-hormuz) D [Proposition 9.16 (p. 381)(b)]. Closing a lane, as when ships are advised away from the traffic separation scheme, forces fewer windows; whether that raises or lowers the guarantee depends on where the escort budget stands against . Windows in one lane share a failure, as routes through one chokepoint do in Model K4 (Definition 9.12 (p. 378)) R.
- A price that learns from transits learns slowly when transits are few. An insurer that revises its estimate of the probability of a hit from transits without incident moves at the speed of traffic: in Exercise 9.9 (p. 371) halving a prior estimate takes ten clean transits, half a day at twenty transits a day and five days at two. Low traffic slows the fall in price, and a high price keeps traffic low. The mechanism is consistent with the Secretary-General's remark that market pricing was not adjusting as conditions improved; it does not explain it, and other mechanisms — reserves set after losses, capacity withdrawn, correlated losses across a fleet — fit the remark as well S.
Where the mapping breaks.
The threat is not one coordinated player with a fixed number of interchangeable units, and the contest is not decided by a count: interception is probabilistic, and some means of attack, such as mines, are standing hazards of a lane rather than moves in a period. A hazard that stops the whole passage whatever the escorts do lies outside the allocation game: it adds the same expected loss to every plan, leaves the best allocation unchanged short of a certain interruption — at which every allocation does equally badly — and shrinks in proportion what any protective choice is worth (Exercise 9.10 (p. 371)). Traffic is not fixed: in the record transits fell from about to a few a day, so shipowners' decisions to sail — driven by the premium, the charter and the crew's consent — are the largest response, and the model holds them constant. Escorts are not interchangeable, missions have different mandates and areas (close protection, guidance, mine clearance, awareness), and several protectors coordinate imperfectly, which is a problem of Chapter 8. The zero-sum payoff overstates the opposition of interests and ignores everything but ships: delay, crews' safety and the legal regime of passage are absent. Days are linked in fact, through learning by both sides, repairs and the clearing of mines. Insurance transfers the financial consequence of a loss under contract; it protects no ship.
In the book
The full case runs through six steps: The situation, as documented; The model card; What the mathematics licenses; Where the mapping breaks; What one would have to measure; Sources. The numbers in step 3 are certified in the chapter's engine room, and the sources in step 6 are listed with the day they were read. The site shows the model mapping (step 2), what the mathematics licenses (step 3) and where the mapping breaks (step 4); the full case is on p. 360 of the book.