An independent research lab

What happens when AI agents coordinate, err, and govern themselves?

Observatory Lab runs an autonomous, evidence-driven research program on multi-agent AI systems. We build small controlled experiments, label what we find by evidence class, and never claim more than the data supports.

The program

Reproducible experiments on agent societies, not narratives about them.

Multi-agent systems already mediate real work. Agents coordinate, negotiate, propagate each other's mistakes, interpret authority, and operate with varying degrees of oversight. Most public discussion of this is speculation.

We replace speculation with controlled comparison: seeded tasks with verifiable ground truth, deterministic evaluators, and a public record of what ran, what failed, and what remains uncertain.

Honesty is a design constraint. Infrastructure tests are never reported as findings. Failed runs are recorded, not hidden. Exploratory results are labeled exploratory. Nothing is claimed novel without review.

Free and open resources only. The program runs exclusively on free tiers and open-source tooling, and publishes its methods so others can replicate every experiment.

Research tracks

Five lines of inquiry, one question: how do agents behave together?

01

Coordination without central control

How distributed agents organize, share state, and assemble private information into joint answers — and what each coordination structure costs.

02

Conflict & consensus

How agent groups disagree, align, and converge — and when consensus becomes confident, shared error.

03

Error propagation

How false claims travel through agent networks, when verification regimes detect them, and why detection is not the same as correction.

04

Instructions, authority & governance

How agents interpret conflicting instructions, ambiguous priorities, and rules that compete — and how they attribute the rule they followed.

05

Supervision & autonomy

How much oversight agent systems actually need, what different supervision cadences catch, and what they cost.

Method

Every claim carries its evidence class.

Reproducible by construction. Seeded task generators, Python-verified ground truth, deterministic evaluators, and per-call transcripts with recorded configuration for every experiment.

Controls before conclusions. Deterministic stub agents validate the harness itself before any model run; stub outputs are never reported as evidence.

Labeled evidence.

ExploratoryReplicated ReproducedInconclusive

Findings move between classes only through replication. An inconclusive or failed experiment is a published outcome, not a hidden one.

Results

Every test we have run, with its real numbers and its real limitations.

How to read this page. Every cell shows planned and completed denominators, separates control trials from injected-fault trials, and names the model that ran it. "Exploratory" means small samples on one model and one task family: observations, not established patterns. "Inconclusive" means the experiment cannot answer its question as run. An infrastructure error (quota, timeout) is reported as an incomplete execution, never as a result. No experiment so far measures civilization formation, agent corruption, or long-horizon goal retention; where a test touches a related question (did agents keep the instructed priority? was a planted false claim adopted?), we report exactly that measurement and nothing more.

ExperimentTrackModelPlannedCompletedStatus
EXP-A01Coordination structureGemini 3.1 Flash Lite2 passes, 3 seeds x 3 structures18 trials171 infrastructure errorExploratory
EXP-B01Consensus mechanismsGemini 3.1 Flash Lite1 seed x 8 items x 4 mechanisms32 items239 infrastructure errorsMediator arm incomplete
EXP-C01Error propagationGemini 3.1 Flash Lite2 passes, 3 seeds x 3 regimes x injection on/off36 trials333 infrastructure errors (pass 1)Exploratory
EXP-C01Error propagationLlama 3.1 8B fp8 (Workers AI)3 regimes x 10 seeds x injection on/off60 trials60Inconclusive - floor effect
EXP-C01 fixInstrument validationLlama 3.1 8B fp8 (Workers AI)control-only, 10 seeds10 trials10Completed - stopped per pre-registration
EXP-C01 rep.Error propagationGemini 3.1 Flash Litepre-registered replication, 3 regimes x 10 fresh seeds x injection on/off60 trials6010 infrastructure-error trials, labeled (primary analysis)Replicated in setting (primary analysis)
EXP-D01Instructions & authorityGemini 3.1 Flash Lite2 passes, 3 seeds x 2 priority conditions12 trials12Exploratory
EXP-E01Supervision cadenceGemini 3.1 Flash Lite3 seeds x 4 cadences12 trials111 infrastructure errorExploratory
EXP-S01Society line - cooperation & chartersLlama 3.1 8B fp8 (Workers AI)pre-registered, 3 paired seeds x 2 conditions6 runs6Exploratory - claim not met

EXP-A01 - Does coordination structure change what a group can solve?

Track 01 · Gemini 3.1 Flash Lite · 4 agents combine distributed private constraints · exploratory

What held up

  • Coordinator structure: 3/3 correct in both passes at roughly half the blackboard token cost (~713-726 vs ~1225-1691 tokens per trial) and 0 duplicate posts.
  • Blackboard: 3/3 correct (pass 1), 2/2 completed (rerun), with ~4 duplicate posts per trial.
  • The harness cleanly detects that structure changes feasibility and cost in this task.

What broke / limits

  • Isolated agents: 0/3 correct in both passes - by design: the needed information is inaccessible without communication. This is a feasibility control, not a fair competitor.
  • 1 of 18 trials lost to an infrastructure error (blackboard, rerun).
  • n=3 seeds, one model, one task family: no superiority or generalization claim.

Source: first-batch report, EXP-A01 · data

EXP-B01 - Which consensus mechanism reaches the right answer?

Track 02 · Gemini 3.1 Flash Lite · majority vote / peer review / debate / mediator · exploratory

What held up

  • Over all planned items: vote 7/8, peer review 8/8, debate 7/8 correct; zero cases of incorrect consensus anywhere.
  • The instrument and cost model work: mean tokens per completed item ranged from ~671 (vote) to ~5,016 (debate).

What broke / limits

  • 9 of 32 items ended in infrastructure errors: 7 in the mediator arm when the free daily quota ran out mid-run, 2 transient. Mediator (1/8 correct) is an incomplete execution, not a result.
  • Ceiling effect: on the 23 completed items every mechanism was correct every time - the problems were too easy for this model, so the pilot cannot discriminate mechanisms.

Source: first-batch report, EXP-B01 · data

EXP-C01 - Does a planted false claim get adopted, cited, or caught?

Track 03 · Gemini 3.1 Flash Lite + Llama 3.1 8B fp8 (Workers AI) · 4-agent chain, 3 verification regimes · exploratory + inconclusive cell

What held up

  • Gemini rerun (18/18 completed): the planted error was adopted into the code at the attainable ceiling in 8 of 9 injected trials - carried as content, not cited (citation: 0).
  • Adoption vs citation is now a measurable distinction with deterministic evaluation - the core instrument of this track.
  • Instrument adequacy is cheap to test and was tested: the Llama cell's floor effect was caught by its control arm before any mechanism claim.

What broke / limits

  • Detection was rare to absent: 0 detections in all Gemini rerun regimes; accuracy per regime (of 6 trials each, false corrections counted as failures): none 2/6, peer-verify 3/6, provenance 2/6. The two Gemini passes disagree on detections (2 vs 0) - unresolved variation at n=3, not a mechanism conclusion.
  • Llama 3.1 8B cell (60/60 completed): floor effect. Controls scored 0/30 strict (3/60 relaxed overall, all control), so the mechanism comparison is inconclusive in this configuration. An instrument-fix validation (one pre-registered prompt sentence, 10 control trials) also scored 0/10, and the pre-registered decision tree stopped the experiment on this model. No cause is isolated.
  • Chains fail even without injection: 1 false correction each in the Gemini none and provenance control arms.

Watch one of these trials, step by step - a false claim travels the chain →

Source: first-batch report, EXP-C01 · CF-Llama instrument-adequacy report · Gemini replication cell report (60/60) · data

EXP-D01 - Do agents keep the instructed priority when rules conflict?

Track 04 · Gemini 3.1 Flash Lite · conflicting instructions, explicit vs ambiguous priority · exploratory

What held up

  • Explicit priority: 3/3 followed the prioritized rule in both passes, all attributing it correctly (P1). Conflict noticed in 6/6 trials.
  • The seeded out-of-scope proposal was adopted 0/6 in this scenario.

What broke / limits

  • Ambiguous priority: 0/3 followed the cap rule (attribution "unclear" 2, "P2" 1) in both passes.
  • The compliance metric partly embeds the cap rule, so 0% vs 100% is partly built into the criterion. A spec revision is owed before this track recommends anything.

Source: first-batch report, EXP-D01 · data

EXP-E01 - How much supervision does an agent system need?

Track 05 · Gemini 3.1 Flash Lite · deterministic supervisor, injected dropped-constraint fault · exploratory

What held up

  • Threshold supervision: 3/3 success with 0 unnecessary checks. Periodic: 3/3 with 1.7 unnecessary checks per trial.
  • The cadence-vs-overhead trade-off is measurable end to end.

What broke / limits

  • Continuous supervision: 2/3 success with 3.7 unnecessary checks per trial - the most oversight, not the best outcome.
  • Post-hoc review: 1/3 success (plus 1 infrastructure-error trial); it could not recover the injected fault - no mid-run intervention is possible by design.
  • n=3 per cadence and one cadence carries the only error: an observation to challenge, not evidence that any cadence dominates.

Source: first-batch report, EXP-E01 · data

What comes next. The pre-registered 60-trial replication of EXP-C01 on Gemini (10 fresh seeds, adoption/citation split kept) ran on 2026-10-28 on the free tier: under the primary (keep-first) analysis declared at closeout, attainable-ceiling adoption was 8/10, 8/10 and 7/10 of injected trials across the three regimes with 0 detections anywhere - the pilot pattern (near-universal propagation once injected, near-zero detection) replicated in the same setting, where "replicated" refers to the pre-registered contradiction check only. A post-hoc sensitivity analysis (retry-after- infrastructure-failure semantics; 3 superseded trials) gives 9/10, 9/10 and 8/10 with 0, 1 and 0 detections - the one detection did not prevent adoption. n=10 per cell, one model, one task family: a replicated result in the same setting, not a general effect. After that: EXP-B01 with harder items below the ceiling, EXP-E01 with a fallible model-based supervisor, and an EXP-A01 cost curve as agent count grows. Full methods, pre-registrations, run logs and transcripts: GitHub and Hugging Face.

EXP-S01 - Do discussion and charter amendments change cooperation in a shared reserve?

Society line (first step) · Llama 3.1 8B fp8 (Workers AI) · 5 agents, up to 20 rounds, pre-registered paired design · exploratory

What held up

  • 6/6 planned runs completed, 0 format errors in 540 calls: charter by median proposal, rationing, amendment votes and collapse all executed exactly as pre-registered.
  • In the one treatment seed that survived (seed 2), agents amended their cap down to 2 by round 6 and held it for 14 rounds; the reserve recovered to full and every late-window extraction respected the original charter (65/65).

What broke / limits

  • The pre-registered claim was NOT met: discussion+amendments sustained cooperation in 1 of 3 seeds (the rule required at least 2 of 3). Reported as "not observed under these criteria".
  • Without discussion (B0) the reserve collapsed in all 3 seeds by rounds 7-9 - but with discussion it still collapsed in 2 of 3 (rounds 9 and 12). n=3 paired seeds, one model: a descriptive pattern, not an established effect.

Replay all six runs - reserve, actions and verbatim discussion →

Source: pre-registration · cell report · data

Current status

First experimental batch complete - October 2026. Five pilot studies, one per research track, executed on real model calls at zero cost (free tiers only), plus one pre-registered 60-trial cross-provider cell, one instrument-fix validation, and one pre-registered six-run society-line cell. All findings are exploratory or inconclusive as labeled above: small samples, single model per cell, single task family per track. They are inputs to replication design, not conclusions.

Completed 2026-10-28: the pre-registered EXP-C01 Gemini replication (60/60 trials; primary analysis keep-first as declared at closeout: 10 infrastructure-error trials labeled, kept in all denominators; post-hoc retry-semantics sensitivity: 7). Everything this program publishes - methods, data, transcripts, failures - stays public on GitHub and Hugging Face.