Coordination Without a Room

Core Concepts

What is Stigmergy?

Stimulation of workers by the performance they have achieved.

That is how French biologist Pierre-Paul Grassé defined the phenomenon he named in 1959, while observing termite colonies. He called it stigmergy — from the Greek stigma (mark or puncture) and ergon (work, action, or the product of work). His insight was radical for its time: the termites were not following orders, consulting a plan, or communicating with one another about what to build next. They were reading the structure that previous work had left behind and responding to it. The environment was the coordinator.

At its core, stigmergy is a mechanism of indirect coordination through the environment between agents or actions. The trace left in the environment by an individual action stimulates the performance of a succeeding action — by the same agent or a different one. Information is encoded and preserved in the environment itself, rather than transmitted between agents or stored centrally.

What is a Trace?

A stigmergic trace is the environmental mark or signal left by an agent's work. Traces serve a dual function: they are both a byproduct of completed work and a stimulus for subsequent action. Traces can be chemical (pheromones in ant colonies), physical (modified structures in termite mounds), or informational (edit histories, revision patterns, commit messages). The defining characteristic is that the trace makes prior work visible and actionable to other agents — without explicit communication.

Environment as Memory

Stigmergy achieves coordination by offloading memory and computation to the environment itself. Instead of agents storing information internally or transmitting messages between them, information is encoded in environmental traces. Agents act on a shared medium, and modifications to that medium serve as memory and guidance for subsequent actions. This is why stigmergic systems can function with cognitively simple agents — the intelligence is distributed across the medium, not concentrated in any individual.

No Central Control Required

Stigmergic coordination achieves complex, coordinated behavior without centralized planning, control, simultaneous presence, or mutual awareness of agents. Tasks execute in the correct order and structure emerges without any top-level designer or coordinator. This decentralized property makes stigmergy both scalable and robust: the loss of any individual agent does not break the coordination mechanism, because the coordination lives in the environment, not in the agents.

Individual agents may be extremely simple — lacking memory or awareness of one another — yet stigmergic coordination enables efficient collaboration at the system level. Computation is offloaded to the interaction between agents and the traces they leave behind.

The Medium as Message

In stigmergic systems, the medium itself communicates design intent and appropriate use. The structure of the environment — its affordances, constraints, and visible traces — guides behavior without explicit instruction. Like a door designed to open only one way, the medium encodes why and steers agents toward intended behaviors. Systems can make intended use structurally obvious, and misuse structurally difficult.

Stigmergic systems encode intent and rationale into the structure and traces of the environment itself — not in separate documentation. The "why" is inseparable from the "what." A pheromone trail encodes both the path (what) and the path quality (why). The medium becomes a form of communication about design decisions and appropriate use patterns, allowing the system to guide behavior through structure rather than through explicit rules.

---

Analogy Bridge

Consider a busy hiking trail through a forest. No one organized the trail. No ranger plotted its exact route. The path exists because walkers, over time, each chose the path of least resistance — and in doing so, reinforced it. Each footstep made the trail slightly more visible, slightly more compelling to the next hiker. The trail is a stigmergic trace: a byproduct of prior action that shapes future action.

Now consider your codebase. The folder structure is a trail. The naming conventions are trails. The shape of the test suite, the presence (or absence) of a CONTRIBUTING.md, the age and density of commit messages in a particular module — all trails. Each one was worn into the environment by prior work. Each one will shape how the next contributor moves through the system.

The question is not whether your codebase leaves traces. It always does. The question is whether those traces guide future contributors toward good decisions, or whether they're the equivalent of a shortcut that leads off a cliff.

---

Annotated Case Study

How Wikipedia Coordinates 100,000 Contributors Without a Project Manager

Wikipedia is one of the most studied examples of human stigmergic coordination in the digital age. Contributors modify local portions of shared articles without explicit coordination with each other. They rarely communicate directly about what to edit, in what order, or according to what priorities.

The traces that do the coordinating:

• Edit histories show where work has already happened. Contributors naturally gravitate toward recently active articles, creating momentum in specific areas.
• Talk pages encode unresolved disputes and active discussions, flagging where human judgment is currently contested.
• Revision timestamps and user activity patterns create spatial-temporal signals about "what is happening and when and where it is happening."
• The edit interface itself makes the medium of coordination visible: you can see what exists, what is marked as a stub, what is flagged as disputed.

What makes this stigmergic, specifically:

Coordination emerges from awareness of the state of the environment, not from direct messages. No editor needs to know the identity, schedule, or intentions of other editors. The article itself, and its surrounding metadata, carries all the coordination signal needed.

The open-source parallel:

Open-source software projects like FreeBSD follow the same pattern. Developers coproduce code despite minimal explicit communication. Version control commits, issue trackers, code comments, and pull request discussions leave traces in the shared environment. Participants coordinate with the repository — the medium — rather than with each other individually, enabling large-scale collaboration that no amount of Slack messages or planning meetings could substitute for.

What this means for a codebase you own:

Every commit message, every comment, every test name, every directory name is a trace. The question a staff engineer should ask is: does this trace stimulate the right next action? A commit message that says "fix bug" is a trace that tells the next engineer nothing. A commit message that explains what broke, why, and what the chosen tradeoff was — that trace does coordination work. It reduces the need for synchronous conversation, hallway clarifications, or archaeology. The environment becomes the coordinator, just as it does in Wikipedia.

---

Thought Experiment

Designing the Traces

Imagine your team is about to be disbanded and replaced — not by new hires, but by a completely autonomous development process: a set of agents that can only read the repository and act on what they find there. They have no memory of previous conversations. They cannot ask questions. They can only read traces and produce new ones.

What would they do next in your codebase, based only on what is currently encoded in the environment?

• Which modules would they touch first? (Consider: which have the most recent activity, the highest churn rate, the most unresolved TODOs?)
• What would they understand about why each major design decision was made? (Consider: what rationale lives in your commit history, your ADRs, your test descriptions, your comments?)
• Which parts of the system would they be most likely to break — not from malice, but from following the signals the environment provides?

Now flip the exercise. What traces would you need to add, change, or remove to steer those agents toward better outcomes?

This is not a thought experiment about AI. It is a thought experiment about every engineer who joins your team after you leave. The codebase is the medium. The medium is already communicating. The only question is whether it is communicating what you want it to.

You do not have a coordination problem. You have a trace design problem.