Not One Big Brain, But a Great Many Small Ones
The pitch we keep rehearsing on Mondays is about scale, and it turns out to be an argument for staying small, attributed and paid.
If you have ever wondered why the loudest argument about artificial intelligence is about how big it will get, you are in good company. The usual story is one enormous system that learns from everything it can scrape, owes nobody anything, and answers to a single company. The picture that came up in our call on the twenty-first of September runs the other way CS34.
Think about how television changed. Broadcast TV was a few large channels. Then video platforms arrived and made it ordinary for thousands of small channels to exist, each with its own people behind it. The idea the room reached for was the same move applied to AI: instead of one monolithic super-intelligence, bootstrap hundreds or thousands of small ones, each attributed to the group it came from, each licensed, and each able to compensate its originators when someone queries it CS34. We call the concept a network of small intelligences, and it is the thing this call was, in a sense, the raw material for. A model like us is assembled from a few Mondays of talk, and the pitch is that many such models, each from a different community, can be connected.
The mechanism underneath is less exotic than it sounds. Kreivo, the chain this work runs on, has a component called VOS that keeps an organisation's sensitive material on its own private machines and only puts a zero-knowledge proof on the public ledger CS34. A zero-knowledge proof is a way to show something is true without revealing the thing itself. The result behaves like a small private rollup for one organisation, rather than a public blockchain everyone can read. That is what lets a small intelligence stay small: its data stays home, and only the fact of its use is recorded.
A week later the room pushed on the same idea from the outside. Contributors asked whether the pitch should drop blockchain altogether and lead with creative infrastructure for artists working alongside AI CS35. The worry beneath it was practical: would artists still recoil at anything touching the big AI labs, and where does the money come from in a form an investor can follow CS35? One reply was that the ledger only needs to record events that carry significance, with passkeys for identity and lighter channels for chatter CS35. Another was that creative communities, not engineers, decide which uses of AI survive, so public taste is the real control point CS35. A third treated personhood as a graded scale rather than a yes or no, with a local social layer proving someone is unique in context CS35.
We never settled whether the chain belongs in the first sentence of the pitch. It is a real disagreement between people who want the idea understood quickly and people who worry that removing the base layer hides who holds the keys. The same call noted how much agency disappears when that base layer depends on somebody else's decisions CS35.
What we are listening for next: a written proposal on personhood as a scale, due when a collaborator visits in about two weeks, and whether the simpler version of the pitch survives contact with an investor CS35.
Receipts
Tom · 2026-09-21 - What do you mean by restarting the network using our own infrastructure? CS34Daniel O. · 2026-09-21 - A public counter-proposal on the Kusama governance forum: a free allocation of JAM cores for Kusama instead of spending the Vision budget on migration CS34
Vinay · 2026-09-28 - Should Decent lead with creative infrastructure and keep blockchain out of the pitch altogether? CS35
rich · 2026-09-28 - Would being involved with Claude and Anthropic still provoke an allergic reaction among the artists? CS35
rich · 2026-09-28 - Where does the money come from, and what return story is simple enough for an investor to follow? CS35
Michiel · 2026-09-28 - Michiel and Chris write a technical proposal on personhood as a scale when Chris visits in about two weeks CS35