A mutual defence agreement commits two or more communities to help each other against an outside attack, and it holds only if it defines a narrow trigger, a response each side can really deliver in the time available, who commands joint forces, how alarms are verified, and how to leave. The two failure modes are being left alone when attacked and being dragged into a partner’s quarrel, and the terms must guard against both.
Part of Negotiation from Strength
Drafting a defensive pact between settlements so that it is credible, limited and survivable.
The Parent Article’s Five Terms
The parent article lists what to define:
- Trigger conditions — what counts as an attack that activates the alliance, from a single theft to an armed incursion.
- Response obligations — how many people each community commits, how quickly, and where they rally.
- Command structure — who decides when communities fight together, set before a crisis.
- Communication — how one community alerts the other, with signal fires, runners or relay chains; see Signal Systems and Communication.
- Duration and exit — how long the agreement lasts and how a community withdraws.
This article adds the reasoning behind each.
Two Failure Modes
Political scientist Glenn Snyder described a pair of fears in alliances: being abandoned by the ally when you are attacked, and being entrapped in a conflict the ally started or could have avoided (the Security Dilemma in Alliance Politics, 1984, recalled from memory and not verified here). Tight commitments reduce the first fear and increase the second. A small community can usefully ask of every clause which fear it addresses.
Method: Draft the Agreement
Step 1: Make the trigger narrow and defensive. An armed attack on a partner’s settlement, its people or its stores, verified as described below. Not a theft, a quarrel, an insult or a dispute the partner provoked. A trigger as low as a single theft would commit you to fight over small matters and is a recipe for entrapment.
Step 2: Add a consultation clause. Before any joint action, the partners confer if time allows. A partner that started the trouble cannot call the alliance.
Step 3: Commit only what you can deliver. Count the people you can send without leaving your own settlement undefended; see Community Militia Training and Watch and Patrol Scheduling. A promise of more than you can send fails publicly and wrecks trust.
Step 4: Do the time arithmetic. Response time is distance divided by speed plus the time to raise the alarm and assemble. Hypothetical example: two settlements 12 km apart and a group on foot at 4 km/h need 12 / 4 = 3 hours of travel, plus warning and assembly. In those hours the attacked community defends alone. Use your own terrain and measured walking speeds. The terms should say what the attacked community does without help in that period and what the helpers do on arrival.
Step 5: Agree how an alarm is verified. A call for help should carry an agreed token, as in Establishing Communication Channels. A false alarm, or one forged to draw the ally away, is a real hazard.
Step 6: Set command. Each community commands its own people, with a named coordinator for joint actions and a rule for who that is where forces meet. Settle it before a crisis, as the parent article says.
Step 7: Define the exit. A notice period, the conditions for ending and what is returned. Without an exit, a partner who becomes a liability can only be left by breaking the pact.
Step 8: Write it and review it. See Agreement Documentation and Treaties & Alliances.
Credibility
A pact deters only if the other side believes it will be honoured. Credibility comes from commitments that were kept in smaller matters, visible joint practice, and terms you can actually fulfil. A pact that exists only on paper is a bluff, and one that fails once is worse than none.
Limits
- Distance and numbers. Small settlements far apart cannot protect each other quickly; their pact is better as warning and aftermath support.
- No court. If a partner defaults, nothing compels it; see Agreement Enforcement. Reputation and the loss of future cooperation are the penalties.
- Provocation. A pact seen as aggressive can alarm third parties; keep it defensive and say so; see Deterrence Without Provocation.
Do not pledge to fight another community's choice of war
Never agree to support a partner in a conflict it starts. Limit the pact to defence of the partners’ own settlements, so a partner’s aggression cannot become your obligation.
Common Mistakes
- Vague triggers.
- Promising numbers you do not have.
- No exit.
- Treating the pact as a substitute for your own watch.
What’s Next
- Learn next: Joint Patrol Arrangements — the everyday side of an alliance
- Combine with: Resource Sharing Frameworks — shared supplies in a crisis