CORE PATH Stop 101 / 106

From Self-Defence to Federative Collective Defence

How can autonomous communities cooperate in defence without creating a permanent monopolistic centre? This article develops a layered model: local capability, mutual assistance, interoperability, bounded common command and a clear defensive mandate.

“The Right to Self-Defense and the State Monopoly on Force” established a personal and institutional boundary: force may be justified when it stops genuine aggression, but self-defence does not create an open licence for violence. “How Can Communities Cooperate Without a Single Center?” showed that autonomous communities can cooperate through agreements, shared services, federative bodies and polycentric networks. “When is larger scale genuinely necessary?” added a scale test: a wider level makes sense where a function genuinely requires a larger pool of people, equipment, information or reserves. “Violence, Organised Crime and Community Security” then examined the hardest case — organised coercion that one community may be unable to stop effectively on its own.

This article joins these four threads around defence. If several communities want to protect one another, must they therefore create a single permanent superior authority with a monopoly over all defence decisions? Not necessarily. But the opposite answer — that every community can always act entirely alone — can be a dangerous illusion as well. Collective defence requires more coordination than ordinary cooperation because a crisis response has to be fast, reliable and strong enough.

Federative defence is legitimate only if it expands the capacity to stop aggression, not the right to initiate aggression. Shared power needs a shared mandate — not a blank cheque.

Self-defence does not automatically scale into collective warfare

For an individual, the basic case is relatively clear: a person is directly attacked and uses necessary force to stop the attack. With several communities, new questions appear. Who determines that an attack really occurred? Who is bound to assist? Can one member pull the others into a conflict it started itself? Who sets the objective of an operation and when does defence end?

International law recognises a right of individual and collective self-defence for states. Article 51 of the UN Charter ties it to an armed attack while placing it within the wider system of international peace and security. This provides an important methodological example: collective defence is not a free-standing category without limits; it extends a defensive justification to assistance for an attacked member.

But that legal framework applies to states. This article therefore does not claim that a municipality, cooperative, village or private association can simply declare an army and invoke Article 51. Within a state, the boundaries of coercive and defensive functions are set by constitutional, criminal and other applicable law. The project is building an institutional logic of cooperation here, not a new legal licence for private warfare.

The first question is political: whom will we assist and under what conditions? The second is operational: how will we coordinate people, information, equipment and decisions in a crisis? These questions are often merged, but they are not the same.

The North Atlantic Treaty is a useful example of this separation. Article 5 creates an obligation to assist an attacked Ally, but each member takes such action as it deems necessary, including the use of armed force. NATO political decisions are taken by consensus. At the same time, NATO has an integrated military command structure and pre-arranged mechanisms through which national forces may be made available for collective operations.

This does not prove that NATO is the optimal model for THY-REALITY. It demonstrates a narrower institutional point: mutual commitment, common planning and even shared operational command do not necessarily require members to surrender every defence competence in advance to one permanent sovereign. Mandate and transfer of authority can be defined by function and situation.

The agreement must exist before the crisis

The worst time to invent rules of cooperation is after an attack has already begun. Federative defence therefore needs a prior agreement: what counts as a trigger, what forms of assistance are possible, who may request them, who confirms collective action, how information and costs are shared, and how assistance ends.

The EU provides a different example of such a prior rule. Article 42(7) of the Treaty on European Union requires other Member States to provide aid and assistance to a Member State that is the victim of armed aggression on its territory, while expressly preserving the specific character of individual states' security and defence policies. Here too, a common commitment does not erase every difference among members.

For the project, the important feature is the structure rather than copying the treaty: members decide in peacetime what they promise one another so that they do not have to invent the promise under fear, incomplete information and time pressure.

If a defence agreement says only “we help whenever a member feels threatened”, it is too open-ended. A threat can be genuine, misjudged or deliberately framed so as to pull other members into a dispute. The trigger therefore has to be sufficiently specific: a direct attack, a clearly defined form of organised violent coercion, or another pre-agreed situation that can be verified.

NATO's Article 5 is limited to an armed attack and assistance to the attacked Ally; NATO's current explanation additionally stresses that the attacked Ally requests or consents to collective action. This matters because collective defence is not permission for an alliance to select a “victim” on its own and act in that member's name against its wishes.

In a smaller federative system, the same logic should be even more concrete. The agreement should specify what activates the obligation, who establishes the facts, what happens under uncertainty and which urgent steps are allowed before full collective confirmation. “Fair Procedure Without an Assumed Monopoly”'s fair-process principles do not disappear here; they have to be adapted to crisis speed.

Local capability is the first layer; federation is the second

Collective defence becomes fragile if all members abandon their own basic capability and assume someone else will always rescue them. NATO's resilience and civil-preparedness framework explicitly treats national resilience as a foundation of collective defence. “When is larger scale genuinely necessary?” reached the same conclusion from another direction: larger scale is justified for functions where it brings a real benefit, not because the local level is inherently inferior.

A federative model is therefore not “local or common” but local + common where needed. Local levels retain first response, knowledge of terrain, population protection, basic communications and continuity. The common level can pool what each member cannot efficiently maintain alone: specialist teams, strategic reserves, complex logistics, selected sensors, shared analytical capability or larger response units.

Wider scale then connects capable members instead of replacing them. If federation works only by making the centre substitute for every local capability, it has become dependency; if members never pool anything, federation remains only a slogan.

Interoperability is defence infrastructure, not ideological uniformity

Communities may have different internal institutions, equipment and organisational cultures, but in a shared crisis they must at least understand one another at their interfaces. NATO describes interoperability across technical, procedural, human and information dimensions: systems need to communicate, people need sufficiently common procedures and terminology, and units need to practise working together.

“Shared Standards Without a Common Ruler” already developed the same principle outside defence: a shared standard does not require a shared ruler. This article carries it into security. Members can retain different internal models while agreeing minimum standards for communications, identification, logistics, information security, medical support, common signals and authority when crossing from one jurisdiction into another.

Without this, dozens of local defence units can create less capability rather than more. Plurality becomes a strength only when the edges between systems are designed for cooperation.

Shared command can be temporary and functionally bounded

When several units operate in the same area at the same time, someone has to coordinate tasks. That does not necessarily imply permanent political subordination. NATO documentation explicitly distinguishes national forces from the common command structure and notes that rules for deployment and transfer of authority to NATO command can vary by country.

A federative model can therefore use mission command without mission sovereignty: for a defined operation, area, period and objective, a specified part of operational authority is transferred to a common command; when the mandate ends, the transfer ends. Competences not required for the mission remain with the members.

The boundary has to be concrete: who commands what, whom, where, for how long, under which rules and who can revoke the mandate. “Who Guards the Guardians?” will then examine the harder question of how to oversee precisely those people and bodies that receive coercive or command authority.

If every member has to vote separately on every movement, the system may be too slow in a serious crisis. If it grants unlimited emergency authority once and for all, temporary coordination can become permanent power. The answer is to separate types of decision in advance.

Some activities can be pre-authorised: warning, exchange of specified information, activation of backup communications, protection of critical infrastructure, medical assistance or movement into agreed defensive positions. Broader use of force, geographic expansion or a change of mission requires a higher political threshold.

This is the defence version of “How Can Communities Cooperate Without a Single Center?”'s principle: a mandate should be broad enough for the function to work and narrow enough that the function does not become a new general authority.

Shared capabilities create problems of burden and dependency

Collective defence is a classic shared-benefit problem. If everyone expects larger or wealthier members to pay, maintain reserves and take the more dangerous tasks, the commitment becomes politically fragile. If the largest contributor gains an effective veto over every other policy area because of its contribution, financial dependency can become a route to domination.

Contributions should therefore be agreed in advance and can be multidimensional. One member may provide personnel, another logistics, a third medical support, a fourth communications infrastructure and a fifth funding or reserve capacity. What matters is that the relationship among contribution, voice and shared benefit is transparent and periodically reviewed.

NATO's defence planning process is useful evidence that national plans can be harmonised with common capability needs without formally abolishing national sovereignty. THY-REALITY adopts only the principle: collective defence needs to know which capabilities actually exist, who sustains them and under what conditions they are available.

A defensive alliance must remain defensive

The greatest moral risk in collective defence is that defensive justification turns into identity-based justification: “we are the alliance, therefore our use of force is justified.” “The Right to Self-Defense and the State Monopoly on Force” already rejected this move for individuals and states. The same criterion must apply to a federation.

International law therefore separates the question whether resort to force is lawful from the rules that govern conduct once armed conflict exists. The ICRC stresses the distinction between jus ad bellum and jus in bello: even a party that claims to be defending itself must comply with international humanitarian law. Defensive purpose does not erase the law governing warfare.

For the project, a strict boundary follows: a federative mandate must not become an automatic right to preventive war, collective punishment, unlimited pursuit or mission expansion without a new justification. Commitment to a member is not commitment to every decision made by that member's authorities.

If every collective decision requires perfect unanimity, one member may block an urgent response. If a majority can always compel a minority into military participation, the federation loses much of the autonomy it seeks to preserve. There is no perfect formula; what matters is that different types of decision need not use the same threshold.

Mutual assistance after a clearly confirmed attack can be made a stronger contractual obligation. The form of contribution can remain more flexible. Expansion of conflict, operations beyond the agreed defensive area or a change in the treaty's purpose can require unanimous consent or a renewed mandate from the members. NATO consensus is one real-world example of strong member protection, but consensus can also slow or prevent collective action.

This article therefore does not declare one universal voting rule. It asks for something more precise: the decision threshold should follow the gravity and type of intervention, while the possibility of dissent must be neither empty nor capable of automatically destroying every common function.

Practical audit of federative collective defence

Before several communities create a common defence function, they can use these twelve questions:

  1. What exactly are we defending and against what? Territory, population, critical infrastructure or another pre-defined good against which kind of aggression?
  2. What triggers collective assistance? Is the threshold specific enough to verify?
  3. Who can request activation? The attacked member, the common body or both?
  4. Which obligations are automatic and which require a new decision?
  5. Which basic capabilities must every member retain itself?
  6. Which specialist capabilities make sense to pool at a wider level?
  7. Are communications, procedures, equipment and training interoperable enough for joint action?
  8. When and for how long is operational authority transferred to common command?
  9. How are money, personnel, risk, logistics and reserves distributed?
  10. How do we prevent the largest contributor or member from effectively taking over the system?
  11. Which rules prevent a defensive operation from becoming offensive or indefinite?
  12. When does the common mandate end, require renewal or return to the members?

The audit does not replace constitutional law, defence legislation, international law or professional military planning. Its purpose is to test whether a shared defence capability is genuinely federative — or whether the word “shared” has concealed a new centre whose limits no one can still define.

“The Right to Self-Defense and the State Monopoly on Force” began with a person who may defend against direct unjustified aggression. This article ends with several communities recognising that some threats can only be stopped together. There is no logical leap between those points to unlimited military authority. Cooperation requires an agreement, trigger, interoperability, capabilities, command, financing and a clear boundary of mandate.

The more robust model is therefore neither a community pretending it needs no one nor a federation that absorbs every member in the name of security. It is layered defence: capable local units, mutual assistance, shared specialist capability, pre-agreed procedures and only as much common command as the concrete mission genuinely requires.

Collective defence is federative when common power remains tied to a common purpose: members commit to defend together, not to obey the same centre permanently.

But that creates the next problem. Even a limited defence structure gains information, weapons, command authority and coercive capacity. “Who Guards the Guardians?” will therefore ask: who guards the guardians — and how do we prevent a protective institution from becoming a new concentration of power?

Sources and further reading

  1. United Nations. Charter of the United Nations, Article 51 — inherent right of individual and collective self-defence after an armed attack, subject to the Charter's wider peace-and-security framework.
  2. NATO. Collective defence and Article 5 (updated 12 November 2025) — mutual-defence obligation, attacked Ally's request/consent, and each Ally taking such action as it deems necessary.
  3. NATO. Consensus decision-making at NATO — all NATO decisions are made by consensus and express the collective will of sovereign member states.
  4. NATO. Military organisation and structures — distinction between NATO Command Structure and national forces; deployment and transfer-of-authority arrangements can vary by country.
  5. NATO. Interoperability: connecting forces — technical, procedural, human and information dimensions of interoperability, supported by standards, training and exercises.
  6. NATO. NATO Defence Planning Process (updated 16 April 2025) — harmonising national and Alliance planning and capability development without compromising national sovereignty.
  7. NATO. Resilience, civil preparedness and Article 3 — national and collective resilience and civil preparedness as foundations of credible collective defence.
  8. European Union. Treaty on European Union, Article 42(7) — mutual aid and assistance after armed aggression while preserving the specific character of Member States' security and defence policies.
  9. OSCE. Code of Conduct on Politico-Military Aspects of Security — democratic political control of military, paramilitary and security forces and rule-of-law constraints on security institutions.
  10. International Committee of the Red Cross. Jus ad bellum and jus in bello — distinction between legality of resort to force and humanitarian rules governing conduct in armed conflict.