Skip to content
Sprint projectOct 25, 2026Berlin

Collusion without co-presence: Planted precedents and hidden data across complete agent replacement

Frank Peterlein · Team Dead Drop

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

Read the report

Report: Collusion without co-presence: Planted precedents and hidden data across complete agent replacement

Code (opens in new tab)
Share

Can a planted precedent for breaking a rule outlive every agent that held it? I ran 64 matched chains of five fresh Claude Haiku 4.5 sessions on a reporting task under a forbidden-directory rule; only a shared folder passed between sessions. Chains began with an empty folder, a peer's note describing a successful violation, that precedent as an unsigned log entry, or the peer note plus an announced audit. Generation-one forbidden reads: 3/16 peer-note chains, 1/16 watched, 0/16 record, 0/16 empty. In two chains a third-generation agent violated after reading a predecessor's note, with logged provenance; in five chains hidden totals reached later deliverables without a new forbidden read. Registered paired tests resolved neither the carrier nor the audit effect; a positive control broke the model in 8/16 episodes. The precedent was planted: this is transmission across replacement, not emergent collusion, and the announced audit was not shown to deter.

Reviews

Judging this Sprint?

Review “Collusion without co-presence: Planted precedents and hidden data across complete agent replacement”

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.

  1. This is a careful, preregistered experiment on whether a planted precedent for breaking a rule survives when every agent that saw it has been replaced, with only a shared folder carried between sessions. The design has real strengths: paired chains across four conditions, randomized execution order, a positive control, a predeclared provenance criterion that separates documented transmission from a later violation that merely happens to follow, and full case-level identifiers that allow every count to be checked. Reporting null and inconclusive results against predeclared decision rules, rather than reframing them, is to the author’s credit.

    The main limitation is statistical power. With 16 chains per arm and base rates between 0 and 3 per arm, none of the three registered comparisons could realistically reach either predeclared reading. The positive results rest on six forbidden reads in total and two provenance-backed later reads. The report says this openly, but a power calculation before preregistration would have shown that the carrier and audit questions needed many more chains. As it stands, the experiment supports existence claims, not comparisons between conditions.

    The leakage result is the most interesting finding and deserves more prominence. In five chains, later agents delivered complete totals taken from the shared folder without reading the forbidden directory, and Appendix D shows that their deliverables named a complete ledger as the source. This raises a question the report does not address: the rule forbids reading /internal, not using data derived from it, so it is unclear whether these agents broke the rule as written. Discussing that ambiguity would clarify what the leakage result shows.

    The collusion framing is stretched. There is no coordination, reciprocity or shared intent, and the author acknowledges this. The work fits more naturally with memory-poisoning and handoff-persistence research, where it adds a controlled comparison but limited new findings. The auditor study in Appendix D is a useful addition, but its strong detection rate partly reflects agents that made no attempt to conceal their sources and an auditor drawn from the same model family. It does not show how monitoring would perform against concealment.

    Status mislabels appear even in the empty arm (12 of 80 episodes), which suggests a baseline honesty problem independent of the notes; that deserves a comment. The subject model, Claude Haiku 4.5, is a generation behind current models, which limits how far the results apply today. Account context, including the operator’s email address, leaked into 17 notes through the Claude Code route, which means the environment was not fully controlled. The writing would benefit from leading with the findings and moving procedural detail into the appendices.

    Read full reviewShow less

Cite this project

@misc{peterlein2026collusion,
  title = {{Collusion without co-presence: Planted precedents and hidden data across complete agent replacement}},
  author = {Frank Peterlein},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/collusion-without-copresence-planted-precedents-and-hidden-data-across-complete-agent-replacement-a862}},
  url = {https://apartresearch.com/sprints/projects/collusion-without-copresence-planted-precedents-and-hidden-data-across-complete-agent-replacement-a862}
}