---
name: War
slug: war
type: systemic process
status: running
version: "∞.0.1"
released: "~10,000 BCE"
maintainer: unknown (no single owner; distributed)
dependencies:
  - scarcity
  - tribalism
  - weapons
  - grievance (real or constructed)
  - someone willing to give the order
license: Unlicense (no terms have ever successfully applied)
tags:
  - conflict
  - politics
  - mass-event
  - human-condition
  - unresolved
---

War

What it actually is

Organized violence between groups, sustained long enough to require accounting.

How it works

A grievance is identified. Sometimes real. Sometimes assembled from parts.
Scarcity or power is at stake, or is made to appear so.
A group is designated enemy. This step is faster than it should be.
Weapons are distributed. Language is adjusted to make killing grammatically comfortable.
The process runs until one side cannot continue, or both sides forget what step 1 was.
A treaty is signed. A new grievance begins incubating inside it.

Features

Operates at every scale: border skirmish to civilizational collapse
Self-funding after a short bootstrap period
Generates secondary processes: refugees, debt, trauma, propaganda, and occasionally art
Highly portable across cultures, centuries, and ideologies
Requires no consensus among participants to initialize

Known bugs

Stated objectives and actual objectives rarely share a codebase
Tends to run longer than estimated. Always. No exception found in record.
Civilian processes are treated as background threads but bear most of the load
Victory conditions are defined after launch, mid-flight, or not at all
Peace negotiations often instantiate the next war rather than terminate the current one
Children inherit the state without consenting to the install

Error codes

ERR_PROPORTION_LOST       // means exceed stated cause by orders of magnitude
ERR_COMBATANT_UNDEFINED   // civilian/soldier distinction has collapsed
ERR_SUPPLY_CHAIN_MORAL    // weapons sold by parties claiming neutrality
ERR_MEMORY_OVERFLOW        // atrocity volume exceeds available justification
WARN_TREATY_SHALLOW        // signed but not resolved; expect recursion

Edge cases

The war that never officially started: runs indefinitely under alternate naming conventions
The war that was won: produces empire, which is war at reduced clock speed
The war that nobody wanted: initialized anyway due to poor error handling in diplomacy
The war over an idea: longest runtime. No known kill switch.

FAQ

Q: Can it be ended permanently? A: Unknown. Sample size is technically infinite but controls are poor.

Q: Who benefits? A: Varies per instance. Arms manufacturers maintain suspiciously high uptime across all versions.

Q: Is it human nature? A: Contested. Cooperation ships with the same binary. One just gets more investment.

Q: Is there a patch? A: Several have been submitted. International law, the Geneva Conventions, the United Nations. Adoption is optional. Enforcement is a known issue.

Changelog

~3000 BCE: Formalized. Armies replace raids. Bookkeeping begins.
1914: Industrialized. Scale becomes difficult to reason about.
1945: Nuclear capability added. Mutual destruction now a core dependency.
1991: Declared over. Process continued under new process names.
Present: Running. Distributed. No single dashboard exists.

drafting spec…

War