Make sense together, using grammars

Recursive.eco

We are aspiring to be a recursive public of stories and meaning structures, which are the very infrastructure of society.

In Christopher Kelty's sense (Two Bits, 2008, available in full online) — a recursive public is one that maintains and transforms the technical and legal infrastructure of its own existence, through the people who use it. Kelty was focused on Open Source. Now we are focused on understanding that responsible freedom might mean harmonizing with the right structures — sometimes open, sometimes closed.

We want a better internet. Not bootstrapped-for-the-pitch but actually bootstrapped, with near-zero infrastructure costs and no monetization gradient pulling on us. Not engineered for engagement — we think a lot of what is dangerous about AI right now shows up exactly where short-term feel-good substitutes for long-term capacity. We want a place where humans can use their humanity to connect — with themselves, with each other, with the ecosystem we are part of.

The recursive structure we have been studying is: contemplate → learn → create → share. The loop closes when what people make here comes back into the commons — that's the Recursive Learning channel.

recursive.eco isn't trying to be the destination. It's a catalyst — a place where a grammar can find its people, and where a channel with enough of its own life can graduate: its own GitHub repo, its own identity, its own creators, syncing back here so what happens there still shows up in the commons. Tarot already lives this way — recursive-tarot is its own repo and its own community now. When that happens, recursive.eco's job shrinks to connective tissue — discovery, the AI layer, the sync — not landlord. (We also build on the open-source commons ourselves — Next.js, Supabase, Cytoscape.js — and mean to keep giving back to it, not just draw from it.)