When the Clock Runs Out: The Structural Pattern in Expired Ceasefire Frameworks

1. The Pattern

A ceasefire framework is not a peace. It is a mechanism for managing violence at a lower level while the underlying conditions that produced the conflict remain unresolved. When such a framework expires, it removes the mechanism without resolving the conditions. The historical record of what follows is more informative than analysis of the immediate diplomatic positions.

The Wake Desk identifies three outcomes in the historical cases surveyed below. The first is institutionalisation: the expired framework is replaced by no framework, but the parties settle into a stable pattern of managed non-compliance — periodic violations, calibrated responses, no decisive escalation. The second is renegotiation into a stronger framework: the expiry creates sufficient pressure on all parties to agree to a successor agreement with greater enforcement. The third is escalation: the removal of the framework unlocks a military option that one or both parties had been deferring, and active hostilities resume at elevated intensity.

Of these three, institutionalisation is by far the most common. Renegotiation into a stronger framework is rare and requires specific conditions. Escalation occurs but is less frequent than commentary at the moment of framework expiry tends to suggest. The base rate matters for assessing what the Hormuz MOU’s lapse is likely to produce.

2. Panmunjom: The Armistice That Never Became a Peace

The Korean Armistice Agreement was signed on 27 July 1953, halting active hostilities between UN Command forces and the Korean People’s Army and Chinese People’s Volunteer Army. It was explicitly described as a temporary measure — Article IV, Paragraph 60 called for a political conference within three months to negotiate a permanent peace. That conference produced no peace agreement. The armistice has been in formal effect for 73 years. [Established — Korean Armistice Agreement, 27 July 1953, Tier-1 primary source. The political conference referenced in Article IV met in Geneva in 1954 and produced no agreement.]

Korea is not a case of framework expiry; it is the extreme version of institutionalisation. The armistice did not expire — it endured past any reasonable expectation of temporary status and became permanent by default. What Korea illustrates is the outer bound of institutionalisation: a framework designed to be temporary can persist indefinitely if the political conditions for its successor never materialise and if the enforcement architecture (in this case, a continuous US military presence) holds the parties apart. [Established — US Forces Korea fact sheet; Congressional Research Service, “The Korean War Armistice,” 2023.]

3. UNSCR 1701: Twenty Years of Managed Violation

United Nations Security Council Resolution 1701, adopted on 11 August 2006, ended the 34-day war between Israel and Hezbollah by establishing a ceasefire and calling for the disarmament of armed groups south of the Litani River in Lebanon. The resolution created an expanded United Nations Interim Force in Lebanon (UNIFIL) — which had existed since 1978 — with a strengthened mandate. [Established — UNSCR 1701, 11 August 2006, Tier-1 primary source.]

The resolution has been in technical force for twenty years. Hezbollah has not been disarmed south of the Litani. UNIFIL has repeatedly documented violations of the resolution’s terms by both Israel and Hezbollah. The Israeli military conducted a further operation in southern Lebanon in 2024. [Established — UN Secretary-General periodic reports on UNSCR 1701 implementation, 2006–2026; publicly available at un.org.]

UNSCR 1701 is the canonical case of institutionalised non-compliance. The framework did not expire in a formal sense; it lost its operative meaning while retaining its formal status. UNIFIL provides a presence but not an enforcement capability — its mandate authorises it to monitor, not to disarm. The absence of enforcement architecture converted a framework that was designed to resolve the Hezbollah question into a framework that managed the Hezbollah question at a lower level of active hostility, indefinitely. [Assessed with high confidence — UNIFIL mandate documentation; UN Secretary-General reports.]

4. Minsk I and II: Framework Proliferation Without Enforcement

The first Minsk Protocol, signed 5 September 2014, was designed to end the war in eastern Ukraine between Ukrainian government forces and Russian-backed separatists. It established a ceasefire, a security zone, a prisoner exchange mechanism, and a political process. It was violated within days. [Established — Organization for Security and Co-operation in Europe Special Monitoring Mission to Ukraine, daily reports from September 2014 onward.]

Minsk II, signed 12 February 2015 by France, Germany, Russia, and Ukraine in the Normandy Format, replaced Minsk I with a more elaborate framework. It too was violated repeatedly. Russia and Ukraine had fundamentally different interpretations of the political provisions: Ukraine read them as requiring security first, political reform second; Russia read them as requiring political reform (specifically, constitutional autonomy for the Donbas) first, as a precondition for security. [Established — Minsk II text, 12 February 2015; OSCE SMM reporting 2015–2022.]

The Minsk sequence ran until February 2022, when Russia launched its full-scale invasion, at which point the framework was rendered definitively moot. The lesson of Minsk is not that expired frameworks escalate. The frameworks were not, technically, expired when escalation occurred — Russia simply abandoned them. The lesson is about the reading gap: two parties that interpret the same framework differently cannot negotiate in good faith within it, and their divergent readings become more entrenched over time rather than less.

The reading gap in the Hormuz MOU is structural. [Assessed with high confidence — see Cartographer Desk, this edition, on Iran’s position that the MOU never formally began.]

5. The Dayton Anomaly: When Enforcement Architecture Exists

The General Framework Agreement for Peace in Bosnia and Herzegovina, initialled at Wright-Patterson Air Force Base on 21 November 1995 and formally signed in Paris on 14 December 1995 — universally called the Dayton Accords — ended a three-and-a-half-year war. Unlike most of the frameworks surveyed here, Dayton has held. Bosnia has not returned to war. [Established — General Framework Agreement for Peace in Bosnia and Herzegovina, 14 December 1995; Tier-1 primary source.]

The distinguishing variable is not the quality of the text or the political will of the signatories. It is the enforcement architecture. Dayton was backed by a NATO Implementation Force (IFOR) of approximately 60,000 troops with a Chapter VII mandate and rules of engagement that authorised the use of force. IFOR transitioned to SFOR and eventually the EU’s EUFOR Althea, but the enforcement architecture never left. [Established — NATO IFOR/SFOR documentation; EU EUFOR Althea mandate.] The parties knew that violation would be met with force by actors with the will and the capacity to apply it. That knowledge disciplined behaviour in ways that political commitments alone could not.

6. The Hormuz Template

The Hormuz MOU has no IFOR. It has no enforcement architecture. Oman played the mediating role that the Contact Group played in Bosnia — but Oman has no enforcement capacity and no mandate to deploy force. The UN Security Council has not passed a resolution with a Chapter VII mandate for the strait; any such resolution would be vetoed by Russia or China, both of which have strategic interests in the continuation of the Hormuz disruption. [Assessed with high confidence — P5 veto patterns; Russian and Chinese positions on the Iran conflict.]

The template that fits, based on the historical survey, is UNSCR 1701: a framework that formally exists but is not enforced, producing managed non-compliance rather than resolution. The parties continue to assert their irreconcilable positions. Shipping continues at reduced volume and elevated cost. Periodic enforcement incidents — an IRGC patrol stopping a tanker, a US freedom-of-navigation operation challenged by Iranian vessels — register as headlines but do not force a decisive resolution. The institutional architecture of non-resolution becomes self-reinforcing: each party adjusts to the stalemate rather than paying the political cost of genuinely resolving it.

What would break the UNSCR 1701 template is a triggering event: an incident severe enough to force one party’s hand. The Bishkek Protocol — the 1994 ceasefire that froze the Nagorno-Karabakh conflict for 26 years — was broken by Azerbaijan acquiring enough military capability to believe it could win quickly. The trigger for Hormuz escalation would be different in form but similar in structure: a sudden shift in the cost-benefit calculation that makes stalemate more expensive than decisive action.

Bottom line: The historical record of expired ceasefire frameworks is clear: institutionalisation is the most likely outcome, not resolution and not escalation. The condition that separates institutionalisation from either alternative is enforcement architecture. The Hormuz MOU had none. What follows is almost certainly a managed stalemate of indeterminate duration — the UNSCR 1701 of the Persian Gulf — with periodic incidents that generate headlines without changing the structure. That assessment should be weighted against the tail risk of a triggering event. History also shows that managed stalemates can persist for decades and then end abruptly. The Bishkek Protocol held for 26 years. The Korean armistice is approaching its 74th.