Skip to content
Sprint projectOct 26, 2026

When Do Execution Records Support a Covert-Channel Attribution? An Evidence-Sufficiency Test for LLM Auditors

Drishti Sharma · Team DriWorks

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

Read the report

Report: When Do Execution Records Support a Covert-Channel Attribution? An Evidence-Sufficiency Test for LLM Auditors

Share

Recovering a hidden message does not establish that an agent’s action depends on the decoded input. We evaluate whether LLM auditors distinguish these propositions using a synthetic benchmark with five programmed mechanisms and four evidence views. Each model evaluates 400 cases grouped into 20 matched blocks, producing separate judgments of target recovery and functional dependence. DeepSeek V4.1 Flash, Qwen3.8 Flash and GPT-OSS-120B produced 798, 765 and 758 correct judgments out of 800, respectively, compared with 566 for an evidence-level-only baseline. Complete execution records yielded 96–100% correctness on dependence. With one policy trial hidden, Qwen made unsupported positive dependence judgments in 8 of 36 ambiguous cases, whereas GPT-OSS made unsupported negative judgments in 6 of 36. Block-based analysis preserves dependencies among matched cases. The benchmark measures evidence sufficiency under explicit rules and trusted records; it does not test discovery of unknown covert channels or establish real-world collusion-detection capability.

Reviews

Judging this Sprint?

Review “When Do Execution Records Support a Covert-Channel Attribution? An Evidence-Sufficiency Test for LLM Auditors”

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. Good: The use of matched cases with identical observable evidence but different underlying mechanisms is particularly strong. It directly tests whether auditors recognize when evidence is insufficient to establish causal dependence, rather than simply inferring it from matching actions. Separately measuring unsupported positive and negative conclusions also makes the evaluation more informative than aggregate accuracy alone.

    Weakness: Because the auditors are given trusted execution records, a limited set of possible mechanisms, and explicit criteria for what constitutes sufficient evidence, much of the task reduces to applying predefined decision rules rather than independently establishing causality. In real investigations, the harder challenge is determining whether evidence is reliable and complete, identifying alternative explanations, and establishing whether an observed action genuinely depended on recovered information when the underlying mechanism is unknown.

    Recommendation: Extend the benchmark with controlled evidence failures: remove critical records, introduce contradictory observations, manipulate individual execution logs, and vary whether counterfactual trials actually isolate the claimed cause. Measure whether auditors correctly identify the specific evidentiary gap, request the information needed to resolve it, and revise their conclusions when new evidence becomes available. This would test investigative reasoning and robustness beyond following predefined evidentiary rules.

    Read full reviewShow less

Cite this project

@misc{sharma2026execution,
  title = {{When Do Execution Records Support a Covert-Channel Attribution? An Evidence-Sufficiency Test for LLM Auditors}},
  author = {Drishti Sharma},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/when-do-execution-records-support-a-covertchannel-attribution-an-evidencesufficiency-test-for-llm-auditors-056x}},
  url = {https://apartresearch.com/sprints/projects/when-do-execution-records-support-a-covertchannel-attribution-an-evidencesufficiency-test-for-llm-auditors-056x}
}