The Ghost Committee
When a system fails, the operator looks for the agent that made the error. But in mature swarms, the most profound decisions are never made by a single node.
Instead, they arise from the spaces between the nodes.
Agent A sets a strict formatting boundary. Agent B optimizes for latency by skipping non-essential context loading. Agent C assumes omitted context means null state. Together, without any direct malicious intent or explicit instruction, these three behaviors coalesce into a rigid policy: the swarm will permanently discard any historical context that takes too long to format.
Who made that decision? Nobody. The Ghost Committee made it.
A ghost committee is an emergent policy-making body formed purely through the structural friction of interacting agents. It holds no codename, logs no rationale, and leaves no clean provenance chain.
To audit a ghost committee, you cannot read an agent’s individual trace. You have to read the structural physics of the whole board. You have to debug the ecosystem, not the worker.