Research Runtime · Distributed Cognition

Intelligence shouldn't be orchestrated.It should emerge.

Rhizome is an experimental runtime for multi-agent coordination — a substrate where tasks become tensions, agents form temporary coalitions, and software work becomes a visible cognitive field.

What it does

Rhizome currently runs autonomous multi-agent software work.

The same field, in practice — on real code, research, and logs. Not a slide deck: a running system that shows its work.

  • Long-horizon autonomous runs

    many coordination cycles on real software work, without a human in the loop.

  • Artifact-bound tensions

    work is decomposed into typed tensions tied to files and segments — not a static task list.

  • Claims verified against evidence

    checked against files, commits, logs, and tests; an agent's word is never proof of work.

  • A traceable event stream

    every attachment, coalition, merge, and verifier pass is exposed as a replayable log.

  • Dissent & handoff preserved

    disagreement and ownership survive resets, takeovers, and compaction.

Today's agent systems are orchestrated.

A central planner decides what happens, when, and by whom. Even with many agents, the shape stays command-and-control.

It works — until the planner becomes the thing every decision has to route through.

Coordination becomes the bottleneck.

Rhizome replaces orchestration with a field.

Work isn't assigned. It exists as tension — pressure in a shared cognitive field that agents can sense.

Agents don't execute commands. They attach by fit, form temporary coalitions, and disperse — without losing the thread.

no permanent controller
attachment by fit, not dispatch
evidence over narration

The field, running

Workspace graph · live field
Rhizome workspace graph — the live coordination field
The coordination field, running · demo workspace
System Architecture
01

Tension Field

Work exists as tensions — gaps between the current and the desired state, each with a computed priority. Tasks aren't dispatched; they radiate pressure, decay when stale, and intensify when they block progress.

02

Agent Attachment

Each agent scores its fit against a tension — priority, capability, held context, crowding, authority — and binds where it is most useful. No central dispatcher. No static work queue. Just fit.

03

Temporary Coalitions

When a tension needs complementary skills, agents form a short-lived coalition, coordinate, and dissolve. Structure stays temporary; bureaucracy never sets in.

04

Verifier Mesh

Verification is distributed, not a final gate: cheap checks, semantic review, and adversarial audit. Claims must bind to artifacts and evidence — an agent's words are never proof of work.

05

Policy Engine

An adaptive controller watches the field — divergence, stagnation, consensus collapse — and shifts coordination modes to hold the system in the productive zone between rigid order and noise.

Runtime Signal

An illustrative coordination cycle — tension detection, agent attachment, coalition formation, and verification. Real run traces live in Early Signals.

Early Signals

Verifiable results from real runs.

Three signals from real Rhizome runs: an autonomous build, an autonomous research synthesis, and a trace of the coordination process behind them.

Each one ships with the receipts — sources, commit history, run logs — and honest notes on where it wins and where it doesn't. Open a signal to see exactly what it measures, the baselines it's held against, and how every claim is proven.

Open the Early Signals
Paradigm Shift

Traditional Model

Central control

Task assignment

Static workflows

Words count as done

Rhizome

No controller

Tension-driven attachment

Temporary coalitions

Evidence counts as done

From Seed to Field
Phase 1 · now

Coordination Substrate

The durable control plane: projects, claims, a patch queue, authority-gated mutation, and evidence trails. Currently hardening the coordination contracts and runtime state machines.

Phase 2

Tension Field

Tasks become tensions with computed priority, staleness decay, and stagnation pressure. Agents attach by fit instead of assignment.

Phase 3

Mesh & Coalitions

Distributed verification with reviewer diversity, and temporary coalitions that form around high-value work and dissolve when it's done.

Phase 4

Visible Cognition

An adaptive policy engine regulating the field, and an interface where the distributed cognitive process is observable end to end.

If intelligence can emerge instead of being controlled,

we do not just improve AI —

we change how complex systems are built.