Self-Organising Agents

The research volume is enormous and the evidence is thin. Multi-agent debate, the most-cited coordination pattern, did not improve reasoning on our tasks and is in the graveyard. What has changed in 2026 is that harness vendors now ship 'swarm' or 'team' primitives, so the pattern arrives in client stacks whether or not it works. Nobody has published a cost-normalised comparison where a self-allocating collective beats the best single agent with the same token budget on a task family we can reproduce. Until that exists this stays a candidate with a trigger, not a field.

Two delivery pods have already been asked to 'use a swarm' by clients who read a vendor blog. The lab's job here is to be able to say no with evidence, cheaply, and to know the moment the evidence flips. If self-allocation does work, it changes how the Backpressure and Auth Broker patterns are designed, because the number of actors becomes a runtime variable rather than a config value.

Agent collectives that allocate their own work will beat orchestrated pipelines only once a coordination cost model exists; until then every 'emergent' result we have seen is a fixed workflow with extra tokens. That is the lab's one-line position on it, which is not the same as an explanation.

The shape the field is converging on, from the most authoritative source in it: Most published multi-agent reasoning gains vanish under token-budget normalisation.signal

This is the section a page most needs a person for, and the one composition is worst at. Nobody has written the plain-language version — what the idea is, in words that assume nothing — and it is the first thing a reader who has never met the term needs.

The lab opened this field on 2026-01-20, and it has not reached mainstream awareness yet. Everything below is what has moved since.

A term arrived: Two major harnesses ship 'agent teams' in the same fortnight That is the earliest reliable signal of a field being born — the vocabulary settles before the capability does.signal

What shipped: Two major harnesses ship 'agent teams' in the same fortnight (Vendor changelogs, 2026-08-04). Tooling arriving is what moves a field from argument to something a team could try.signal

What changes, concretely: Fixed-role multi-agent pipelines (planner, worker, reviewer) work and are in production; they are orchestrated, not self-organising.signal

Nothing is shipped as a default yet, so adopting this is a piece of work rather than a configuration change. That is usually the difference between a field being interesting and being used.

The binding constraint is reliability: it works and is not yet dependable enough to put near a customer. Everything upstream of that is solved and everything downstream of it is waiting.

It is also gated on another field: eval-harnesses — A cost-normalised, reproducible benchmark appears (frontier lab, top-three harness, or a peer-reviewed paper with code) where a self-allocating collective beats the best single agent by >10 points at the same token budget on a task family we can run; Argus canary reproduces the margin within a week.; backpressure — x-backpressure-queue or a successor publishes a fan-out pattern that holds under a runtime-variable actor count; until then a collective cannot be deployed safely regardless of accuracy.. Until that trigger fires, effort here compounds slowly.clustercluster

Something here has already been killed: Multi-agent debate improves reasoning on our tasks, on a type 2 run stopped on day 11 when the owner was pulled onto the memory bench and the claims-triage eval it was using was re-baselined under a new extractor, leaving the two completed conditions incomparable with the planned third.graveyard

The argued case against it is the red team's, further down this page, and it is deliberately one-sided — this section is what stands in the way mechanically, not what somebody thinks of it.