---
name: Conflict
slug: conflict
type: process
status: running
version: 4.2.1
released: "prehistory"
maintainer: human-nervous-system
dependencies:
  - desire
  - scarcity
  - other-people
  - memory
license: Proprietary (cannot be uninstalled)
tags:
  - interpersonal
  - internal
  - structural
  - universal
  - load-bearing
---

Conflict

What it actually is

Two or more [[desire|desires]] occupying the same space, refusing to move.

How it works

Conflict initializes when two agents (or one agent across time) hold incompatible models of how things should be. It does not require malice. It does not require misunderstanding. It runs fine on pure, well-intentioned incompatibility.

The process is roughly:

Resource or value collision detected
Each party generates a position
Positions are broadcast, usually imprecisely
Each party receives a corrupted version of the other's signal
Both parties respond to the corrupted version
See step 3

Resolution is a fork in the loop, not the default exit condition.

Features

Runs on any substrate: nations, families, the self, team Slack channels
Fully distributed: no central server required
Generates heat as a byproduct, occasionally light
Compatible with love, grief, and most other emotional runtimes simultaneously
Scales from one person arguing with their past self to geopolitical collapse
Produces art in roughly 30% of cases

Known bugs

Parties frequently argue about the wrong thing entirely, the real issue compiling silently in the background
Memory is mutable: each agent's logs of the same event diverge over time, both convinced theirs is the source file
"Winning" often triggers a delayed regret subroutine
Avoidance mode (conflict.suppress()) does not resolve the underlying process; it forks it underground
Resolution reached under exhaustion is frequently mistaken for resolution reached by understanding

Error codes

CONFLICT_001  Position stated; no listener found
CONFLICT_002  Listener found; no position understood
CONFLICT_003  Resolution achieved on surface layer only
CONFLICT_004  Third party injected, scope increased
CONFLICT_005  Parties merged identities with positions; exit blocked
CONFLICT_409  Resource already claimed by both
CONFLICT_000  Conflict with self. No external handler available.

Configuration

conflict:
  mode: overt | covert | cold | hot | passive
  duration: acute | chronic | geological
  resolution_style: negotiation | avoidance | rupture | synthesis | attrition
  third_party_involved: false
  stakes: low | moderate | existential
  memory_auditing: unreliable  # always

Edge cases

Two parties who agree on everything can still generate conflict via boredom
Conflict that appears resolved at the interpersonal layer may continue running at the structural or systemic layer indefinitely
Some conflicts are not meant to be resolved; they are meant to be held, the way a suspension bridge holds tension

FAQ

Does conflict mean something is wrong? No. It means something is alive.

Can it be prevented? You can prevent specific instances. The process itself ships with the base package.

What ends it? Usually: one party exhausted, one party leaving, both parties touching the actual thing underneath the stated thing, or enough time passing that the original resource no longer matters. Occasionally: genuine understanding. Rare but documented.

Is it always bad? It is the mechanism by which change enters systems that would otherwise calcify. The star does not shine without pressure.

"I wasn't angry at him. I was angry at what he represented. He happened to be standing there." submitted via anonymous user report

drafting spec…