--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
drafting spec…
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: Mob Behavior slug: mob-behavior type: emergent social process status: running version: "∞.0.1" released: "prehistory" maintainer: no one. everyone. dependencies: - fear - anonymity - in-group signaling - a spark license: Public Domain (cannot be revoked) tags: - collective action - social contagion - group dynamics - psychology - crowd ---
A temporary operating system that installs itself over individual judgment, runs hot, and rarely uninstalls cleanly.
Mob behavior bootstraps through a predictable sequence. A grievance (real or constructed) is introduced into a sufficiently dense social environment. Anonymity or perceived safety-in-numbers reduces personal accountability. Emotional contagion spreads faster than information. Individual identity partially suspends. The group acquires a temporary shared will, which is nobody's will exactly.
The process is not irrational in the narrow sense. Each participant is responding to real local incentives: social belonging, threat reduction, the intoxicating clarity of a shared enemy. The irrationality is emergent. It lives at the aggregate layer, not the node level.
This is the bug that looks like a feature until the logs come in.
| Bug | Description | Frequency |
|---|---|---|
target_drift | Mob re-targets mid-execution, sometimes randomly | Common |
leadership_capture | A single actor hijacks collective energy for private ends | Very common |
memory_loss | Participants sincerely do not recall their own behavior | Universal |
righteousness_overflow | Moral certainty exceeds available evidence | Default state |
friendly_fire | Members turn on each other after primary target is exhausted | Occasional |
MOB_ERR_001: Insufficient grievance. Process fails to initialize.
MOB_ERR_002: Target too abstract. Crowd requires a face.
MOB_ERR_003: Rain. Physical dispersal. State resets.
MOB_ERR_004: Camera present. Behavior modifies unpredictably.
MOB_ERR_005: Participants individually confronted. Process halts.
MOB_ERR_003) is unavailable as a circuit breaker. See also: the internet.Q: Is this always bad? A: No. Collective action sometimes produces necessary outcomes. The process itself is neutral the way fire is neutral.
Q: Can it be stopped once running? A: Friction helps. Time helps more. A credible counter-signal from inside the group is the only reliable interrupt. Outside signals are often treated as further evidence of conspiracy.
Q: Who is responsible? A: Legally: unclear. Morally: distributed in a way everyone finds convenient.