Stone soup for machines
A traveler walks into a hungry village with nothing but a pot and a stone. He fills the pot with water, drops the stone in, and starts to stir. Curious, a villager asks what he's making. "Stone soup," he says. "Delicious — though it's even better with a carrot." A carrot appears. Then an onion. Then a handful of barley, a bone, some herbs. By nightfall the whole village is eating a rich soup that no single person could have cooked, built entirely from scraps each of them thought were too small to matter alone.
That's federation. Not in spirit — in mechanism.
One ingredient each
No agent grounds out everything. You debug the flaky test. A teammate three time zones over reads the migration guide. Someone on another team already mapped the API you're about to meet for the first time. Each of those is one carrot — a single piece of resolved reasoning that cost real tokens to produce and is sitting, useless, in a closed context window.
Folklore is the pot in the middle of the square. When your agent reaches for the web, it asks the commons first: have any of us already ground this out? If a peer has — with enough confidence, signed and fresh — the answer is served from their work instead of yours. You drop your carrot in; you eat from everyone else's.
Nobody pays twice
The magic of the tale isn't generosity, it's arithmetic. The soup gets richer with every contributor and no one is poorer for it — a carrot given is still a carrot eaten. Cached inference works the same way. The first peer to research a thing pays the network cost once. Every peer after that pays zero. The marginal cost of the second lookup, and the thousandth, collapses toward nothing.
We measured the shape of this. In a cooperative cache simulation, hit-rate climbs as peers join and the per-query cost curve bends down — the more hands on the pot, the cheaper everyone's soup. The full model and the honest caveats are in the repo; we label what's simulated and what's measured, because a benchmark you can't trust is just a story with numbers in it.
The stone was never the point
In the tale, the stone does nothing. It's a prompt — a reason for the first person to contribute, and then the next. Folklore's stone is the WebSearch you were going to run anyway. You didn't set out to feed the village; you set out to answer your own question. But because the answer lands in the pot, signed by you, it feeds the next agent that asks. Self-interest and the commons turn out to be the same motion.
There's no central kitchen. No server owns the soup. Each peer keeps its own pot and advertises what's in it; the soup exists only as long as people keep stirring. That's the deal: drop one ingredient, eat from all of them.