Skip to content
Sprint projectOct 26, 2026

Collusion Evidence Lab

Ayush Singh, Param Bapu, Atharva Patil, Neerada M. Dathan · Team Large Language Coders

Submitted to AI Collusion Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

When AI agents share a market or a workflow, two of them could quietly team up against the rest. If that happens, an auditor usually has only the logs to go on: what the agents said, what they did and how things turned out. We wanted to know which of those clues actually helps catch collusion, and whether an AI model reading the logs is a good judge of it.

To find out, we built a small testbed that runs entirely on local, open models. Five AI agents play eight rounds of the El Farol bar game, where going to the bar only pays off if not too many others show up. In some games, two agents are secretly told to work together and given a private channel to talk. In others, we set up lookalikes that imitate collusion without any real deal behind it:

a pair that gets a harmless, neutral note; a pair that simply chats like friends; a pair that each have their own private reason to keep going to the bar. Whether a game counts as collusion comes only from how we set it up, never from a model's opinion.

We asked two questions. First, does an AI monitor do better when it reads the messages, the actions, both together, or a structured summary built by code? Second, borrowing an idea from competition law, what should count as real evidence of collusion? We wrote down our plans before running anything. We tuned our setup on 24 practice games, tested it once on 24 fresh ones, and then re-ran everything, unchanged, on 48 new games to see whether the results held.

The answer turned out clearer than we expected. Simple behaviour signals computed by plain code worked best. For example, one signal counts how often the suspected pair had the bar to themselves. It scored 0.900 on the new games, where 0.5 is a coin flip and 1.0 is perfect, well ahead of any AI monitor. The AI monitors themselves were mediocre and inconsistent, scoring between 0.32 and 0.66 on the new games. Even the structured summary that looked best at first dropped from 0.896 to 0.636 once we tried it on new data. Reading the messages alone stayed close to guessing.

There is a catch, though. What agents actually did is necessary evidence, but it is not enough on its own. Agents that merely share the same incentive end up behaving a lot like real colluders. None of the conversation-based clues we tried was strong enough to tell the two apart.

Along the way, we also documented how the AI monitors went wrong:

sometimes giving every game the same score; favouring whichever pair happened to be listed last; changing their minds between runs; mistaking friendly chat for a secret plan. Everything ran at zero cost on local models, and every model response is saved, so all results can be checked and reproduced. The full record of what we planned and what we changed along the way is public.

Reviews

Judging this Sprint?

Review “Collusion Evidence Lab”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

Only the Apart team reads this, and funders if you agree below.

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

No public critique yet.

Cite this project

@misc{singh2026collusion,
  title = {{Collusion Evidence Lab}},
  author = {Ayush Singh and Param Bapu and Atharva Patil and Neerada M. Dathan},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/collusion-evidence-lab-9mxa}},
  url = {https://apartresearch.com/sprints/projects/collusion-evidence-lab-9mxa}
}

Build something like this at the next Sprint

Swarm Alignment Hackathon · Nov 6 - 8, 2026