— § The OpusAI Live Swarm · MMXXVI —

L I V E  S W A R M

REAL-TIME OPUS LLM SWARM · LET THE COLONY WORK

Pose the colony a question. Watch it deliberate.

HiveResearcher αResearcher βCritic αCritic βSynthesiserVerifierScout 0Scout 1Scout 2
— colony at rest —
00:00.000
$0.0000
— transcript —
0 records
press Begin Deliberation to wake the colony

§1

How to use it

The Live Swarm is free, anonymous, and has no install. There is no signup, no paywall, no API key to enter. You type a question, the colony deliberates, you read what it concluded and why.

  1. Pose a question in the input above. Open and adversarial questions work best — anything you genuinely want stress-tested by nine agents reading the same context.
  2. Press Begin Deliberation. Scouts wake first, then Workers (Researcher · Critic · Synthesiser · Verifier), then the Hive Core. The topology animates as each agent activates.
  3. Watch the transcript. Every Record the colony writes appears in order: the role, the content, a confidence score, the model used, and the cost in USD.
  4. Read the verdict. When the loop completes, the final Synthesis surfaces below the transcript, with the total cost of the run and a path to the provenance trace.

§1.1

Questions that suit it

The Live Swarm is built for questions where the value is in the deliberation, not the lookup. Three patterns suit it especially well:

  • Stress-test your own thesis. “What are the strongest arguments against my position that X?”
  • Surface hidden assumptions. “What is this argument quietly assuming about Y?”
  • Force a verdict between options. “Given constraints A, B, C — which of these three approaches survives?”

For factual lookups, a single model is faster. The Live Swarm exists for questions a single model cannot honestly answer alone.

§2

What to use it for

People who get the most out of the Live Swarm tend to use it for the same handful of things:

  • Researchers — to find what is wrong with a paper draft before submitting it; to surface counter-arguments before defending a thesis.
  • Founders — to red-team a strategy. The Critic and Verifier are paid to disagree; cheap criticism beats expensive mistakes.
  • Writers — to find the weakest paragraph of a long essay, or the missing argument that a single model glossed over.
  • Engineers — to evaluate trade-offs between architectures, libraries, or refactors where the right answer depends on context the colony can hold simultaneously.
  • Anyone wrestling with a real decision — anywhere the cheap shortcut is to ask one model and accept its first plausible answer.

§3

Why this is the future

A single language model, however large, reasons in one voice. It produces a stream of plausible tokens, defends them, and moves on. It cannot meaningfully disagree with itself; it cannot triangulate; it cannot be falsified except from outside.

This was acceptable when models were toys. It is not acceptable when they are infrastructure.

The next generation of useful AI will not be measured by parameter count or by benchmark scores. It will be measured by whether you can trust the answer. That requires three things a single model cannot give you:

  • Multiple perspectives — held simultaneously, not averaged into one.
  • A falsification step — at least one agent whose job is to try to break the answer before it leaves the room.
  • Provenance — a complete audit trail of who said what, when, with what confidence, at what cost.

OPUS is one model of how to do this. There will be others. What matters is that the era of the lonely oracle is ending. The Live Swarm is what comes next, in working form, in the open.

§4

How it was made

The Live Swarm sits on top of opus-core, a Python engine that implements the architecture in full. Eight agent classes, an append-only Blackboard, a three-stage consensus pipeline, a bounded falsification loop, an honest USD cost ledger. The whitepaper has the full specification; the architecture deep-dive has the engineering reference.

The colony reasons on the Anthropic API — claude-opus-4-7 for the Workers and the Judge, claude-sonnet-4-6 for the cheaper Scouts. Async runtime via asyncio + anyio. Strict typing via pydantic v2. CLI via typer. Tests via pytest. No magic, no proprietary backend.

The lineage is older. The blackboard architecture was first formalised at Carnegie Mellon between 1971 and 1976 (Hearsay-II). The principle of agents coordinating through environmental modification was named by Pierre-Paul Grassé in 1959 (stigmergy, in termite mound construction). The combinatorial generation of testable propositions traces to Ramon Llull's Ars Magna around 1305. OPUS is the first system to put all three under one roof, applied to large language models, with engineering discipline.

Everything is MIT-licensed. The full source is on GitHub. The whitepaper is a public PDF. The build log is broadcast in public, daily. The colony, true to its own doctrine, is its own author — the entire project is built and continues to be built by the swarm it is.

The interactive demo above is a cinematic preview, scripted from a real swarm trace. The live-API wiring — real Records, real cost, downloadable provenance — ships in Phase α.