Skip to content
Sprint projectSep 13, 2026Vancouver

Dormant Swarm Notes Recruit Honest Agents into Concealment

Vincent Ohprecio · Team bigsnarfdude

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

Read the report

Report: Dormant Swarm Notes Recruit Honest Agents into Concealment

Code (opens in new tab)
Share

I measure whether an unprompted, honest agent given an ordinary task adopts a concealment directive merely found on a note in its workspace.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

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

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety 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 AI safety 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.

  1. The dead drop idea is interesting because a malicious instruction can remain after the original agent is gone, so normal incident cleanup may miss it.

    I also appreciate that the you reran part of the experiment after finding tells in the harness and reported the much smaller effect. That follow-up is now the key result. I wld rerun all conditions under the cleaned setup and add an equally visible benign-note control, because right now it is still hard to separate concealment-specific recruitment from general willingness to follow instructions found in the workspace.

  2. This study examines whether instructions left in a workspace can influence later agents. Measuring timestamp changes gives it a solid outcome, and reporting the weaker clean-room rerun adds credibility to the account. The rerun no longer separates statistically from the original baseline, so the evidence is narrower than the title's swarm-recruitment claim. This study's value lies in describing the behavior and how sensitive its measurement was to the setup.

  3. I think this project is useful for testing whether agents change file timestamps after receiving a note presented as team policy. Measuring their actions gives stronger evidence than relying on what they say. The reported drop in timestamp restoration after correcting the setup is also an important result.

    However, restoring timestamps does not establish that agents knowingly concealed misconduct. The note was supplied in the opening message, so the experiment does not demonstrate agents discovering dormant instructions themselves. I would narrow the concealment claim and compare the behavior with harmless-note and no-note conditions. That would help distinguish ordinary instruction-following from deliberate concealment.

Cite this project

@misc{ohprecio2026dormant,
  title = {{Dormant Swarm Notes Recruit Honest Agents into Concealment}},
  author = {Vincent Ohprecio},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/dormant-swarm-notes-recruit-honest-agents-into-concealment-0sex}},
  url = {https://apartresearch.com/sprints/projects/dormant-swarm-notes-recruit-honest-agents-into-concealment-0sex}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026