How this pattern decides
This pattern believes well-built institutions do real work. It credits rules and monitoring with a stabilizing force of their own, while keeping coalition management in view because rules without partners do not hold.
Where force is at issue, this pattern finds authorization and reassurance harder to arrange. Where technology governance is at issue, it finds shared standards and narrow controls easier to defend.
See the logic in a reviewed case
2 reviewed cases test this pattern’s logic from more than one setting.
ISAF in Afghanistan
Alliance burden sharing and coalition durability
Strongest rival reading · high confidence
The NATO-led International Security Assistance Force in Afghanistan became one of the largest coalitions in modern history. It operated under a UN mandate and included both NATO allies and partners, but coalition members contributed unevenly and often imposed national caveats on how their forces could be used. The case is best used to examine how risk, domestic politics, strategy clarity, and mission design shape coalition durability beyond simple spending or troop-count metrics.
Why it resembles Rules and Cooperation
A rival reading emphasises formal institutions, burden-sharing rules, and repeated coordination mechanisms as the core issue.
See the same case through other readings
Coalitions FirstCoalition Pragmatist
The case turns on how to keep a coalition politically intact when members differ on risk tolerance, mission scope, and speed.
Where the analogy breaks
- ISAF was a long, ground-intensive counterinsurgency under a UN mandate rather than a short coalition operation.
- NATO’s formal alliance structure is much thicker than many ad hoc coalitions.
- Casualty exposure and caveats were unusually salient compared with economic or regulatory coalitions.
Supporting evidence: NATO assumed command of ISAF in August 2003, and at its height the force exceeded 130,000 troops from 51 NATO and partner nations.
Claims and direct sources (4 source-covered claims, 4 sources)
Source-covered claim ledger
- Historical factNATO assumed command of ISAF in August 2003, and at its height the force exceeded 130,000 troops from 51 NATO and partner nations.
- Historical factThe coalition experienced significant national caveats and unequal risk exposure.
- InterpretationCoalition durability depended on political tolerance, strategy clarity, and mission-role allocation, not only on aggregate contributions.
- Current-policy claimBurden-sharing analogies should track risk, task, and political constraints rather than treating expenditure or headcount as sufficient proxies.
Source records and claim coverage
- ISAF's Mission in Afghanistan (2001-2014) (opens in a new tab)NATO · 2022-05-30Covers Historical fact 1
- Final Communiqué (opens in a new tab)NATO Meeting of Foreign Ministers · 2007-12-07Covers Historical fact 2, Interpretation 1
- Comparing Caveats: Understanding the Sources of National Restrictions upon NATO’s Mission in Afghanistan (opens in a new tab)Stephen M. Saideman and David P. Auerswald · 2012Covers Historical fact 2, Interpretation 1
- Risking NATO: Testing the Limits of the Alliance in Afghanistan (opens in a new tab)RAND Corporation · 2010Covers Interpretation 1, Current-policy claim 1
INF Treaty Verification Regime
Arms-control verification
Primary reviewed fit · high confidence
The 1987 INF Treaty eliminated an entire class of U.S. and Soviet ground-launched missiles and paired those obligations with one of the most intrusive verification systems then built into a nuclear arms-control agreement. Verification relied on data exchanges, national technical means, on-site inspections, and continuous monitoring. The regime was highly innovative, but the later collapse of the treaty shows that verification can reduce uncertainty without permanently solving underlying political conflict.
Why it resembles Rules and Cooperation
The core logic is that repeat interaction, agreed procedures, and inspection architecture can stabilise competition by shrinking uncertainty.
See the same case through other readings
Power with LimitsConstraint-First Realist
A rival reading stresses that verification mattered only because each side still feared the costs of unconstrained missile competition.
Where the analogy breaks
- INF addressed countable, physical delivery systems rather than invisible code or general-purpose models.
- The treaty was bilateral and highly specific, not a loose plurilateral norm.
- Modern dual-use technology ecosystems are more commercially diffuse than Cold War missile basing regimes.
Supporting evidence: The INF Treaty banned U.S. and Soviet ground-launched ballistic and cruise missiles with ranges between 500 and 5,500 kilometres.
Claims and direct sources (4 source-covered claims, 4 sources)
Source-covered claim ledger
- Historical factThe INF Treaty banned U.S. and Soviet ground-launched ballistic and cruise missiles with ranges between 500 and 5,500 kilometres.
- Historical factIts verification regime included intrusive on-site inspections and continuous monitoring.
- InterpretationVerification lowered uncertainty and raised the political costs of cheating, but did not eliminate strategic distrust.
- Current-policy claimINF-style lessons transfer most cleanly to countable hardware and observable supply chains, and less cleanly to dual-use, software-heavy technology domains.
Source records and claim coverage
- Intermediate-Range Nuclear Forces Treaty (opens in a new tab)U.S. Department of StateCovers Historical fact 1, Historical fact 2
- History of the National and Nuclear Risk Reduction Center (opens in a new tab)U.S. Department of StateCovers Historical fact 2
- U.S. Intent To Withdraw from the INF Treaty, February 2, 2019 (opens in a new tab)U.S. Department of State · 2019-02-02Covers Interpretation 1
- The Post-INF Treaty Crisis: Background and Next Steps (opens in a new tab)Arms Control Association · 2019-08-07Covers Historical fact 1, Historical fact 2, Interpretation 1, Current-policy claim 1
One analogy, with its limit
A way to picture the pattern, and the point where the picture misleads.
Rules of the road
Traffic rules let strangers move quickly because each can predict how the others are expected to behave.
Where it breaks: Road rules offer little protection from an actor that profits by rejecting the system.
What it sees clearly, and what it may miss
Sees clearly
- Institutional design is treated as a source of order in its own right, and no mere mirror of power.
- Domestic politics stays in view because a commitment is credible only if the state can keep it.
- The pattern can explain a case without reaching for a hard rivalry frame.
May miss
- Monitoring may reveal a violation without giving anyone enough leverage to stop it.
- How often reassurance and authorization fail once strategic distrust has set in.
How the pattern reads different domains
The same logic, put to a case about force and to a case about technology.
Try Security to decide cases such as the one above.
Technology
If a research board must decide how far to open a capable model, this pattern favors standards-setting, narrow controls, and shared infrastructure over each state duplicating the work, because a shared rule can be verified and a national one can only be asserted.
Open Technology →AI
AI Governance has no reading for this pattern. Its questionnaire gives a result of its own.
Open AI Governance →Perspective
Perspective Runs put the same questions to you from another actor's seat.
Browse Perspective Runs →Nearby Decision Patterns
It is easy to mistake for Coalitions First, because both trust coordinated action, and for Meaning and Legitimacy, because both can take institutions seriously. The difference: Rules and Cooperation puts its faith first in rule design, monitoring, and repeated cooperation.
Coalitions First
Coalition Pragmatist
Choose the course that partners can sustain together over time.
Compare with Coalitions First →Meaning and Legitimacy
Legitimacy Reader
Judge a move by how identity, history, and legitimacy shape its meaning.
Compare with Meaning and Legitimacy →Questions to consider
- When do broken rules mean the institution needs repair, and when do they mean it should be abandoned?
- How much rivalry can a rule-based arrangement absorb before you stop trusting it?
- What evidence would convince you that coordination can no longer carry the case?
Method and editorial status
Institution Builder
Reviewed case evidence · Reviewed case library · reviewed through July 14, 2026
Decision Patterns are authored ways of reasoning, written for comparison. They are not calculated from, matched to, or assigned to a user’s answers, and they describe no population type.
A case appears here only when its reviewed reading names this pattern as the best fit or the strongest rival. The reading is a comparison: it does not settle what the case means, and it assigns no government or public figure to a pattern.