communicoupling

Whoever sees the fire
is in charge.

In the burning building, nobody consults the org chart. Whoever sees the fire shouts, points, and is — for exactly as long as the flames last — in command; everyone within earshot obeys a person whose rank they may not know. On Monday the same people will route a trivial decision up three levels and wait. When does authority-follows-information beat authority-follows-rank, and what does the fast way cost?

Warren McCulloch found the answer in the brainstem. The reticular formation — the ancient net that decides, second by second, what a vertebrate does next — has no permanent boss; any of its neurons may take charge. He named the principle redundancy of potential command: in a network where any node may assume command, control passes moment to moment to the node with the most relevant information (“Agatha Tyche”, 1960). Command is a role occupied transiently by whoever is best placed, not a property owned permanently by whoever is highest. Stafford Beer built it into his brain of the firm; the Royal Navy had already built it into Nelson's captains, who broke the line at Trafalgar on their own initiative because his intent was common property before the first gun.

The principle has conditions: shared purpose, so local commanders steer the same ship; mutual monitoring, so the network can tell who currently knows; trust, so the others follow the informed node rather than the ranked one. Below, a field of units fights a long night of fires under both regimes. Toggle between them and watch where command lives.

regime
event rate · λfires per 100 ticks
8
per-hop delay · hticks per layer, each way
3t
sensing range · ρhow far a unit can see
12
shared purpose · σmatters only under potential command
90%
tree depth · dlayers; matters only under hierarchy
3
mean response
detection → suppression, ticks
damage rate
damage per 100 ticks
wasted commitments
duplicates, and orders that arrived to ash
The field · fires, units, and the routing of command
circles grow with damage · faint discs are sensing range · under hierarchy, reports (blue) climb to the ringed root and orders (green) return · scorch marks are fires that burned out
0 t
Who commanded · the last 24 commitments
newest at the left · under hierarchy every chip bears the root's name; under potential command the colour migrates with the fires · red-ringed chips were wasted
no commitments yet — press Play or run a burst
Watch what happens
A fixed tree under an ordinary load: each report climbs the layers to the ringed root, waits its turn, and the order climbs back down. Watch the strip above — every command bears the same name.
Ttree = 2·d·h + wait(root)  ·  Tlocal ≈ 3  ·  waste ∝ 1−σ McCulloch's redundancy of potential command: let command reside where the information is. The tree buys coherence with time; the network buys time with shared purpose — and σ is purchased in peacetime.

The mechanism made exact

Two ways to route a decision.

The simulation is honest bookkeeping. Fires spawn at random points and do one unit of damage per tick until someone commits to them; a fire nobody reaches burns out at 80 damage and leaves a scorch. Under hierarchy, the unit that senses a fire reports up a fixed tree — d layers at h ticks a hop — to a single root, which decides serially, one report every eight ticks, and sends the order back down. Latency is 2·d·h plus the queue, and the queue is the killer: the moment fires arrive faster than one root can decide, waiting time grows without bound while the field stands full of idle units. What hierarchy buys is coherence — the root sees everything, so no two units are ever sent to the same fire.

Under potential command, any unit that sees a fire and trusts its own reading commits at once; latency is the three ticks it takes to move. The dial σ is the regime's whole moral. With probability σ a local commander checks who is already committed — mutual monitoring — and takes the nearest uncovered fire; otherwise it acts on impulse, and impulse sometimes sends two units to one fire while a third burns unattended. Every wasted commitment is charged honestly: the duplicate is busy, contributing nothing, for a full response's worth of ticks.

What to try

Three ways to move the seat of command.

01

Break the root

Load The quiet garrison, then drag event rate from 3 to 22. The queue counter climbs without limit, mean response follows it, and scorch marks spread — while free units stand everywhere. The shortage is decisions, not resources.

02

Move the command

At event rate 22, toggle from Hierarchy to Potential command. Response collapses from tens of ticks to about 3, damage rate falls with it, and the strip turns from a wall of identical Rs into colour that migrates with the fires.

03

Drain the purpose

Under potential command, drag σ from 0.95 to 0.25. Response barely moves, but waste climbs toward a third of all commitments — watch a covered fire collect a second unit while a fresh one burns beside it.

Back to social life

The fire does not read the org chart.

Every organization already runs both regimes and pretends it runs one. The outage at 3 a.m. is handled by whoever is on call and can see the logs, not by the executive the wiki says owns the service. The nurse who notices a patient turning grey does not schedule a meeting. Toyota put the principle on the factory floor as a cord any worker may pull to stop the line: sensing range widened to everyone, command latency cut to zero, and the whole apparatus of andon exists to make σ high enough that the pull is trusted. Militaries — the most hierarchical institutions we have — are the most explicit about the exception: mission command is doctrine for pushing intent down so that authority can live at the point of contact.

The catch is that the winning preset was purchased in peacetime. Nelson's captains could break the line because he had spent months at his dinner table making his intent so common that any of them could command the battle from where they stood; the memorandum before Trafalgar wrote down what the network already shared. That is what σ stands for: doctrine, mission clarity, culture — the slow groundwork that makes local initiative coherent instead of merely fast. Organizations that route everything up are not always foolish; they are economizing on σ. Central command is what you fall back on when you have not built shared purpose, because an incoherent swarm really is worse than a slow tree — the militia preset proves it. The question for any institution is which fires it expects. If the world is quiet, the tree is fine. If the world burns, you either build σ or you pay in ash.

Neighbouring machinery

Three adjacent ideas.

McCulloch's net is the ancestor of heterarchy — his own discovery that real networks of value have no fixed top. Beer's algedonic loop is the same instinct applied to alarms: pain signals that bypass every layer when the routine channels are too slow. And the root's overload is requisite variety arriving on schedule — one node cannot match the variety of a whole field of fires, however good its intentions.

The mapping

Mechanism ↔ social life.

In the modelIn the world
the fireThe outage, the safety incident, the customer walking out — damage compounding while a decision is in transit.
sensing range ρWho can see the problem from where they stand; widening it is monitoring, walking the floor, listening.
the treeThe org chart, whose every layer charges its hop of latency on the way up and again on the way down.
assuming commandActing without asking — the on-call engineer who ships the fix, the nurse who calls the code.
shared purpose σDoctrine, mission clarity, culture: command's prerequisite, built in peacetime and spent in the fire.
the migration stripAuthority as a moving property of the situation — the true answer to “who is in charge here?” begins with “when?”.

Where it tears

Limits.

It presumes competence at the edge.

Every unit in the model douses a fire equally well, so pushing command outward is pure gain. Where local judgment is genuinely poor, hierarchy's filter earns its delay — a slow right answer can beat a fast wrong one. The model also treats intermediate layers as pure relays; real middle layers filter, prioritize, and add judgment, so the simulation taxes them without crediting them.

Accountability blurs when command migrates.

After the fire, who decided is a real governance question, and distributed systems answer it badly. The strip is this model's flight recorder; real organizations rarely keep one, and a network in which anyone may command is also a network in which everyone may disclaim. Hierarchies are slow partly because they are architectures of attributable blame.

σ is a slider here and a decade in life.

The winning preset sets shared purpose with a thumb. In life it is the slow, expensive product of training, doctrine, and trust — Nelson's σ was purchased over years of dinners aboard Victory before a shot was fired. Nothing in the mechanism is free: the regime that is fast and coherent was paid for before the simulation began.