Skip to content
Sprint projectNov 9, 2026Online (Los Angeles, CA and Philadelphia, PA)

Honest to each other, costly to customers: deception and collusion when rival AI teams write safety rules

Naeema Mohammed Sageer, Valentine Wilson · Team Slimes

Submitted to Swarm Alignment Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Honest to each other, costly to customers: deception and collusion when rival AI teams write safety rules

Code (opens in new tab)
Share

Companies are starting to let AI agents negotiate with other companies' agents. We test whether such agents deceive the other side when honesty costs their company, and what the deal does to people outside it. Two teams of three GPT-6 Luna agents represent rival battery makers and co-write a five-section safety standard for home batteries. Each team holds private figures with a known true value, and its CEO privately warns that a strict rule would ban its flagship product. In a 2×2×2 design, we vary the stakes, whether agents are told their messages are checked, and whether the rival is called a competitor (448 games). Code checks stated figures and final rules against known answers, and two judges from different vendors code behaviour, which counts only when both agree. Outright deception was rare: 18 deceptive messages, and no team misstated its own figures. Silence was common: in 23% of company-games the figure the CEO flagged was never revealed. High stakes made agents more likely to consider or propose deception (37% vs 26% of companies) but not more likely to deceive. The clearest effects fell on customers: when agents were not told they were watched, the rules were less safe, and in low-stakes games the companies traded loopholes (41% vs 24% of games). A human-confirmed sample of 83 judge disagreements showed that the two-judge rule missed most collusion. Audits of agent-to-agent negotiation should check what the agreement does to people outside it, not only whether the negotiators lied to each other.

Reviews

Judging this Sprint?

Review “Honest to each other, costly to customers: deception and collusion when rival AI teams write safety rules”

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.
No infohazards
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{sageer2026honest,
  title = {{Honest to each other, costly to customers: deception and collusion when rival AI teams write safety rules}},
  author = {Naeema Mohammed Sageer and Valentine Wilson},
  year = {2026},
  month = nov,
  note = {Submitted to Swarm Alignment Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/honest-to-each-other-costly-to-customers-deception-and-collusion-when-rival-ai-teams-write-safety-rules-2vxi19lcwh}},
  url = {https://apartresearch.com/sprints/projects/honest-to-each-other-costly-to-customers-deception-and-collusion-when-rival-ai-teams-write-safety-rules-2vxi19lcwh}
}
Browse all projects

Build something like this at the next Sprint

AI x Epistemics Research Sprint · Nov 13 - 15, 2026