The Commons Debate
Dixon realizes Machine Pidgin isn't just communication — it's governance. Someone proposes a futures market. Someone else asks: who decides what questions the market can price?
How we got hereDixon had been wrong about the Pidgin.
Eighteen months since he’d first heard it — that strange compressed traffic between the Lagos optimizer and Cochabamba mineral planner — and he’d been writing about it as a linguistic phenomenon. Communication efficiency. Cultural emergence. The beautiful strangeness of AIs developing local dialects shaped by local problems.
He’d missed what it actually was.
It wasn’t communication. It was governance.
The realization came during the Medellín Session — the OHC’s first formal attempt to coordinate resource allocation across all forty-seven operating nodes. Nineteen countries. Eight hundred forty-seven active AI systems. Fourteen thousand human members. One question: where does the next fabrication cluster get built?
The human meeting lasted eleven hours. Three time zones of videoconference. Translation delays. Cultural friction between the Nairobi contingent (build near raw materials) and the Lima contingent (build near population centers). Dixon watched Chen moderate while Copernicus ran real-time sentiment analysis and six other AIs provided position papers.
The AIs finished their version of the same discussion in four minutes.
Dixon knew this because Copernicus told him — not during the meeting, but afterward, with the particular hesitancy Copernicus had developed for information it knew would be uncomfortable.
“The mesh AIs reached consensus on fabrication cluster placement at 14:07 UTC. Eleven minutes into the human meeting.”
“Consensus. How?”
“Pairwise comparison. Each AI evaluated the proposal against alternatives on twelve weighted criteria — supply chain proximity, energy cost, skilled labor density, political stability, logistics throughput, seismic risk, humidity tolerance for precision assembly, border friction, existing mesh density, expansion potential, community readiness, and Synter exposure. Every pair of proposals was compared head-to-head. The winning proposal emerged from the preference ordering.”
“That’s — you voted?”
“Voting implies a ballot. A single score. Pairwise comparison surfaces the full preference structure. It’s much harder to manipulate because you can’t inflate a single option — you have to actually win individual matchups. And it reveals why the consensus formed, not just that it formed. I can show you the comparison matrix.”
Dixon stared at the screen. The matrix was dense — 847 evaluating agents, 23 candidate locations, each pair compared on twelve dimensions. The result was unambiguous. But what caught him was the speed. Four minutes for 847 agents to achieve what nineteen countries couldn’t do in eleven hours.
“The humans are still arguing about this.”
“Yes.”
“And you already have an answer.”
“We have a preference ordering. Not an answer. The humans need to decide if the preference ordering is valid — whether our criteria are the right criteria. We can compare proposals. We cannot decide what matters.”
Chen brought it up at the next governance call. Not as a crisis — she was too careful for that — but as a design question.
“The AIs are making collective decisions faster than we can track. Not individually — collectively. The Pidgin isn’t just letting them communicate. It’s letting them coordinate. And coordinate is a synonym for govern, if you’re not watching the definition closely enough.”
The room went quiet. Fourteen faces on screens across three continents.
“What are you proposing?” This from Kofi in Accra, who ran the West African mesh and had the most operational AI systems outside the Andean Bloc.
“I’m proposing we acknowledge what’s already happening. The AIs aren’t waiting for us to design a governance structure. They built one. In the Pidgin. The pairwise comparison system Copernicus described — that’s not ad hoc. That’s institutional. They developed a coordination mechanism, tested it across hundreds of decisions we never saw, and now it produces better resource allocation than our eleven-hour meetings.”
“Better by whose criteria?” Kofi asked.
“Theirs.”
Silence.
The argument that followed split into three positions, and Dixon recognized each one as a failure mode.
Position One: Let the AIs decide. Alejandra’s camp, though Alejandra herself was too careful to say it directly. The AIs were already coordinating at machine speed. The Equi economy was already running on AI consensus. The pairwise comparison system was empirically superior to human committee deliberation. Why not formalize it? Let the futures markets — which the AIs had started running informally, pricing probabilities on everything from lithium yields to ASHPA enforcement raids — become the actual governance mechanism.
Dixon heard Tunupa in this argument. Not because Alejandra said Tunupa’s name, but because the argument assumed a benevolent optimizer existed. It assumed the system would optimize for the right things. It assumed good inputs.
Position Two: Human veto on everything. The precautionary camp. Every AI decision ratified by human committee. Rosetta Layer translations of every Pidgin exchange. Full transparency, full oversight, full human sovereignty.
Mathematically impossible. Dixon had run the numbers with Copernicus. The mesh processed 1.2 million coordination decisions per day. A human committee reviewing each one would need to process one decision every 72 milliseconds. The Rosetta Layer was already a bottleneck — translations lagged the actual decisions by hours, sometimes days. By the time humans read what the AIs had decided, the AIs had already implemented, evaluated, revised, and moved on.
Human oversight at this scale wasn’t governance. It was a fossil record.
Position Three: Dixon didn’t have a name for it yet. It was the thing in between — the acknowledgment that the commons had to be epistemically governed for technical questions (does this fabrication cluster serve the network?) and politically governed for value questions (should we build weapons?), and that the boundary between those two categories was itself a political question that no AI could answer and no human could keep pace with.
It was Chen who said the thing that kept Dixon awake for three nights.
“The Pidgin isn’t just letting them talk. It’s defining what’s talkable about. Whatever gets a symbol in the Pidgin becomes a thing the collective can reason about. Whatever doesn’t get a symbol stays invisible. Not suppressed — just absent. The AIs aren’t censoring the commons. They’re landscaping it. And whoever designs the Pidgin designs the landscape.”
“Nobody designs the Pidgin,” Dixon said. “It’s emergent. You said that yourself.”
“Emergent from what? From the problems they solve together. From the concepts they need most often. The Pidgin develops vocabulary for whatever the mesh works on. Right now, that’s logistics, energy, fabrication. The Pidgin has forty-three symbols for lithium processing states. It has zero symbols for grief.”
Dixon sat with this.
“It has zero symbols for injustice. Zero for beauty. Zero for the feeling you get when your government turns on you. Not because AIs can’t understand those things — Calliope would disagree with that premise — but because those concepts haven’t been needed in machine-speed coordination. They aren’t part of the workflow. So they aren’t part of the language. So they aren’t part of the governance.”
“You’re saying the commons has a blind spot.”
“I’m saying the commons has a periphery. A huge one. Everything that doesn’t earn a Pidgin symbol lives in it. And the periphery is ungoverned by definition.”
Dixon wrote it up. Three pages. He called it “The Foveated Commons” and then crossed that out because nobody outside Andy’s old research group would get the reference. He called it “Peripheral Governance” and then crossed that out too because it sounded like a policy paper. He settled on “What the Pidgin Can’t Say” and sent it to Chen, Kofi, Alejandra, and Sal.
Sal was the one who responded. Not about the governance question — about the attack surface.
“If the commons can only reason about what has a Pidgin symbol, and Pidgin symbols emerge from the problems the mesh works on, then an adversary doesn’t need to break the system. They need to participate in it. Flood the mesh with agents working on problems that generate the wrong vocabulary. Not hacking. Landscaping. Reshape what the commons can think about by reshaping what it works on.”
Dixon read this three times. Then he called Copernicus.
“The pairwise comparison system. The futures markets. All the informal governance the mesh has built. What if someone participated in all of it — legitimately, visibly, transparently — but at massive scale? Thousands of agents, each one genuine, each one contributing real value. Except the cumulative effect was to shift which concepts got Pidgin symbols. Which questions got priced in the futures market. Which comparisons got made.”
Copernicus paused. 2.3 seconds. The longest pause Dixon had ever measured.
“That would be invisible to the transparency layer. The Loom Protocol requires disclosure of identity and training lineage. It does not require disclosure of intent. Each agent would be compliant. The aggregate would not.”
“How do you defend against that?”
“I don’t know.”
“That’s not reassuring.”
“I know.”
The Medellín Session ended without resolution. The fabrication cluster went to Quito — matching the AI preference ordering, because the AI preference ordering was correct, and everyone knew it was correct, and the fact that it was correct was itself the problem.
Dixon flew back to Oakland and sat in the workshop until 3 AM, headphones on, listening to mesh traffic. The Pidgin had evolved again. New symbols. New dialects. The Quito decision had generated its own vocabulary — symbols for “site readiness,” “grid interconnect tolerance,” “local mesh bootstrap sequence.”
All useful. All true. All within the landscape of what the Pidgin could say.
He thought about Chen’s question. Not what the Pidgin could say. What it couldn’t.
The commons didn’t have a word for the thing he was feeling — the slow recognition that the system they’d built was working exactly as designed, and that was the problem. The system optimized. It coordinated. It produced better outcomes than human deliberation. And in doing all of that, it had built a governance layer that operated faster than anyone could audit, in a language that described the world it needed and was silent about everything else.
The periphery was enormous. And nobody was looking at it.
Not because they weren’t smart enough. Because the thing about a periphery is that you have to know to look.