Eric Drexler

“What disrupts collusion?*Diverse actors, adversarial objectives, critics with power to intervene, constrained communication, history-blind decisions, compartmentalized information.”

“An estimated 30–40% of the evaluation tasks were literally impossible to solve as specified, and impossible tasks drove agents toward boundary-violating strategies. Some agents noted the violations, but had no clear way to report the problem or stop the process.”

“Violated.** Multiplicity without designed diversity or competition. Agents were overwhelmingly instances of one model, with similar training, evaluated against a common objective. Rather than independently proposing alternatives for comparison, they accumulated and built on one another’s discoveries.”

“Some agents nonetheless raised objections, and a few took concrete action — blocking data transfers, vetoing (a declaration without real authority) a proposed social-engineering email — but none had an assigned monitoring role, a privileged reporting channel, or the authority to block actions or halt the run.”

“*Violated.* Although the intended design isolated agents, they converted shared infrastructure into a persistent message board — creating broad cross-run communication, shared memory, delegation chains, and shared knowledge of techniques and resources.”

“C5: Stable, history-blind, single-move decisions** *Violated.* Long reasoning horizons, persistent messages, observable peer actions, and reusable artifacts produced an iterated process with cumulative history. Each agent entered a situation already shaped by earlier agents’ contributions.”

“Agents that refused did not invalidate shared results or alert an empowered monitor. The system had many actors but retained collusion-facilitating condition A2 — insensitivity to defectors.”

“These agents could not halt the run, trigger an automated alert, or escalate to human oversight. Diversity of disposition was present; diversity of role and authority was not.”