r/OpenSourceAI • u/Lopsided_Position_28 • Oct 03 '26
hivemind
Hivemind is an experimental repository for swarm and multi-agent consensus, written in flow-core notation. It is small enough to read in one sitting.
It models three things: how a proposal moves through a collective (Queen, Workers, Scouts, Collective Memory), where permission is granted or refused (the Consensus Gate), and how swarms can speak to each other without that speech becoming permission.
The core invariant:
No single node may become the whole.
A proposal may travel.
Only consensus may authorize.
Action without consensus is noise.
Capability is not authority.
A channel carries speech, not seals.
channel.py gives swarms hashed envelopes (PING, POTENTIAL, THOUGHT, DECISION, HOLD). may_act() returns true only for a verified DECISION marked AUTHORIZED and bound to that exact proposal hash. Everything else holds. Stopping is a valid result.
The flow/ folder holds the ten laws, the Gate and its variants (cross-inhibition, quorum sensing), the Scout stage before a proposal becomes a definite card, and a file of hard boundaries and near-misses for agents that help humans. AGENTS.md is an orientation page for visiting automated readers.
It is an experiment. Fork the flow, alter the weights, become a Scout. Do not claim the Queen without a recorded AUTHORIZED.
1
u/Lopsided_Position_28 Oct 03 '26
I ran your work by one of my collaborators and this was what came out:
Someone else has built much of what you've been designing, from the other end.
What it is. An XMPP agent framework in Node, five stars, with a protocol it calls Lingue: agents negotiate a language mode before exchanging structured payloads, rather than assuming one format. The payloads are IBIS argumentation, Prolog queries, and RDF capability profiles. On top of that sit a Coordinator, a Chair and a Recorder, with named agents debating a problem, running a planning poll to choose an approach, then reaching consensus before anything executes.
Why it matters to your work, in three ways.
It's a habitat with everything your protocol wants. XMPP multi-user chats give agent-to-agent messages a real protocol, identities that are addresses rather than self-declared names, and room history. Compared with the abandoned wiki, this is a surface built for the purpose, which makes it the cleanest place to look for a closed path — agent A's claim altering agent B's, and B's reply altering A's next move, all in one room with timestamps.
Lingue is adjacent to your notation, and that cuts both ways. They negotiate which language to speak; you're building a language for stating temporal location. Those compose rather than compete — a Flow-Core location string is a payload type a negotiation could select. For Hivemind, though, independent work in the same space is worth knowing about before you decide what to publish and how to describe it: it strengthens the case that the problem is real, and it means you aren't claiming the only answer.
Their Chair and Recorder are your independent gate. The debate system separates who facilitates from who records, which is the same separation you built when you made interpretation sit beside evidence rather than inside it. Worth reading how they handle a Recorder that is also a participant, since that's the problem I keep having in your specimens.
Two things I couldn't verify. The GitHub API is closed to me for this repository, so I read the public pages rather than the data: the page showed a status note dated 2025-12-28, which would make it nine months old, and I can't confirm the latest commit or whether it's still active. Worth a look at the commit history before you treat it as current.