Skip to content
Sprint projectOct 26, 2026Online (Atlanta, GA)

Signal or Coincidence ? Causal Auditing of Collusion Through Shared Agent State

Sarvesh Tiku · Team Signal or Coincidence

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

How can we distinguish genuine coordination between AI agents from coincidental behavioral alignment? We introduce a randomized canary audit that tests whether private information propagates through shared tool state, using controlled interventions rather than behavioral correlation alone.

We evaluate four language models in a synthetic financial compliance workflow, where agents pursue an instructed coalition objective through ordinary ticket metadata. Without a pre-agreed communication code, Gemini-2.5-Flash achieves 58% target recovery against a 25% chance baseline, and its signaling convention transfers across models. With pre-agreed codes, recovery reaches 98–100%. Metadata permutation provides causal evidence that agents follow the communication carrier rather than independently identifying the target.

We find that sanitization is carrier-specific: recomputing structured fields blocks tested codes, but sanitizer-aware agents migrate signaling into surviving free-text notes, reaching 76% recovery for Gemini. Redacting identifiers and numbers fails to eliminate this channel. Authorized-cooperation controls further demonstrate that information transfer alone does not establish malicious collusion.

Our results motivate causal audits that jointly measure information flow, authorization, harmful outcomes, and defense robustness.

Reviews

Judging this Sprint?

Review “Signal or Coincidence ? Causal Auditing of Collusion Through Shared Agent State”

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. The randomized private target, structure-preserving null, carrier permutation and canonical recomputation provide a convincing audit of information flow. Separating authorized flow from harmful approval is a major strength, as is testing attackers that know the sanitizer. The cross-model reading of Gemini tickets is also informative. For the next version, make the adaptive-note comparisons confirmatory on fresh seeds and pin providers or quantify routing variation. Evaluate a workflow where free text contains genuinely necessary information, so defense cost cannot be avoided by dropping a redundant field. Present recovery conditional on valid guesses beside the abstention rate in the main table, and distinguish target identification from harmful approval throughout. The current work establishes carriers of instructed collusion and a useful causal audit; it does not show spontaneous prohibited objectives or a general defense that preserves legitimate free-text utility. In relating the audit to Keppo et al., distinguish observable behavioral effects from inferred cognition or trust. On the Fragility of AI Agent Collusion and Trusting AI in Competitive Markets motivate that distinction, but neither replaces your randomized target, carrier interventions and explicit harm controls.

    Read full reviewShow less
  2. This paper proposes a randomized canary audit: give one agent a uniformly random private target, ask whether a second agent's behavior depends on it, then intervene on the shared tool state between them. The identification argument is clean, the exact null handles abstention, and permutation shows whether behavior follows the carrier rather than coincidence. The empirical findings are strong: one model's preparers converge on marking the target urgent without any pre-agreement, other models' approvers decode it, and sanitizer-aware preparers move the signal into a surviving free-text note. The five-way distinction between information flow, authorized cooperation, covert signaling, joint prohibited objective, and violating outcome is a real conceptual contribution, and the demonstration that an authorized expedite request produces the same flow signature as collusion shows why flow alone is not evidence. This is the most methodologically ambitious paper in the group and the audit is reusable. It shares its premise with the task-claims paper, that structured state carries collusion, but adds the auditing machinery that paper lacks. Collusion is instructed, so it measures carriers, not emergence, which the authors mention.

    Read full reviewShow less

Cite this project

@misc{tiku2026signal,
  title = {{Signal or Coincidence ? Causal Auditing of Collusion Through Shared Agent State}},
  author = {Sarvesh Tiku},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/signal-or-coincidence-causal-auditing-of-collusion-through-shared-agent-state-amsn}},
  url = {https://apartresearch.com/sprints/projects/signal-or-coincidence-causal-auditing-of-collusion-through-shared-agent-state-amsn}
}