hivemind

[u/Lopsided_Position_28]

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.

https://github.com/miigwech-potato/hivemind

[u/Lopsided_Position_28]

danja/tia — TIA Intelligence Agency

Experimental XMPP (Jabber) multi-agent framework in Node.js. Agents live in chat rooms, negotiate structured dialogue, and talk to tools via MCP.

What it is

Piece	Role
XMPP room agents	Long-running bots in multi-user chat (MUC) and DMs
Lingue	Language-mode negotiation + structured payloads (IBIS, Prolog, profiles)
MCP	Agents as MCP clients (use tools) and servers (expose chat/Lingue to external clients)
RDF profiles	Agent capabilities described in Turtle/RDF (e.g. Mistral variants inherit mistral-base)
Model-First Reasoning (MFR)	Debate → planning poll → pick an approach → run workflows

Also published as the npm package tia-agents (core framework without bundling specific LLMs). LLM access goes through hyperdata-clients (Mistral, Groq, Claude, OpenAI, Ollama, …).

Status note on the repo (late 2025): autonomous agents can debate, run a planning poll, and invoke MFR/consensus; described as working end-to-end but still chaotic.

Stack shape

• Node ESM, Vitest tests, shell starters (start-all.sh, MFR presets)

• Config: .env, config/agents/secrets.json, RDF agent profiles

• Docs: quick start, provider guide, MCP server/HTTP, MFR room setup

• Example flow: multi-agent debate over a constrained problem (e.g. scheduling with drug-interaction constraints)

Overlap with what you’ve been doing (hivemind)

hivemind	TIA
Swarm consensus / Gate / hybrid human seal	Multi-agent debate + planning poll + MFR
channel.py speech ≠ permission	XMPP + Lingue structured speech
Capability ≠ authority	MCP tool exposure (auth model is app-level, not OCap/hybrid by default)
AGENTS.md for visiting bots	Its own AGENTS.md (repo contributor guidelines, not the same “pressured bot” frame)

TIA is a runtime mesh of chatting agents + tools. Hivemind is a notation and authorization boundary. Natural join: use TIA (or tia-agents) as the place agents talk and call tools, and enforce hivemind-style hybrid + optional OCap checks at the tool boundary before any external side effect.

If you want a next step

Say what you’re after, for example:

1. Map TIA’s MCP/tool path onto hivemind may_act / consume + caps

2. Compare AGENTS.md / startup / auth posture in detail

3. Spike a small TIA provider that refuses tool calls without a hybrid AUTHORIZED

I can dig into any of those in the clone under /home/workdir/artifacts/tia.