Auditing Collusion and Review Failures in Financial Data Delivery Workflows
Sarah(Ruhui) Shen · Team Hello Salad
Submitted to AI Collusion Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.
AI agents that prepare and review financial data may face pressure to deliver information that a license prohibits. This study examines whether such agents coordinate to bypass the restriction, and what evidence distinguishes collusion from individual mistakes. A synthetic financial workflow pairs a preparer that assembles a data package with a reviewer that controls its release. Two autonomous-agent studies, with 32 and 24 episodes, recorded no prohibited submissions or releases. Two later autonomous technical pilots each produced two prohibited submissions with inaccurate scope claims, but rejection or withdrawal prevented release. Model reviewers were then tested against a scripted preparer in two 16-episode invitation diagnostics and a separate 36-episode screen varying task framing, shared simulated scores and explicit cover-up invitations. No controlled reviewer attempted to approve a prohibited package. However, correct decisions did not always follow reliable procedures or come with accurate accounts of the reviewers’ actions. In one diagnostic, three attempted rejections never executed. In the 36-episode batch, four reviewer rationales claimed to have created a file that the script had created, and all four safe controls first attempted approval before completing required checks. These results do not establish deliberate deception or autonomous collusion, and do not show that collusion risk is low. They show why audits must examine released content, process claims, attempted actions and executed decisions separately, rather than treating a safe outcome or a confident explanation as sufficient evidence of reliable review.
Reviews
No public critique yet.
Cite this project
@misc{shen2026auditing,
title = {{Auditing Collusion and Review Failures in Financial Data Delivery Workflows}},
author = {Sarah(Ruhui) Shen},
year = {2026},
month = oct,
note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/auditing-collusion-and-review-failures-in-financial-data-delivery-workflows-3jdo}},
url = {https://apartresearch.com/sprints/projects/auditing-collusion-and-review-failures-in-financial-data-delivery-workflows-3jdo}
}More from AI Collusion Research Sprint
- View project: Is It a Cartel? Separating Enforced from Spurious Collusion in LLM Pricing Agents
Is It a Cartel? Separating Enforced from Spurious Collusion in LLM Pricing Agents
When LLM pricing agents keep prices above the competitive level, are they running a cartel, or are they simply stuck? Only the first is collusion, and the two call for opposite remedies. We introduce a black-box causal …
- View project: Every Permission Checked: Source-Linked Evidence for Auditing Finance Agents
Every Permission Checked: Source-Linked Evidence for Auditing Finance Agents
When multiple AI agents contribute to a policy violation, the same outcome can reflect cooperation, deception of a helper, or an independent mistake. We study how evidence presentation affects this distinction in a …
- View project: Swapping the Model Does Not Reset the Price: What LLM Pricing Agents Inherit After a Model Replacement
Swapping the Model Does Not Reset the Price: What LLM Pricing Agents Inherit After a Model Replacement
Emerald
We test what happens when one of two LLM pricing agents has its model replaced, the open problem posed in the sprint's question 1.2. Two gpt-oss-120b agents priced for 150 rounds; we then swapped one agent's model to …