Skip to content
Sprint projectFeb 2, 2026Toronto, Canada

Blind Audit

Giles Edkins, Owen Walker · Team Blind Audit

Submitted to The Technical AI Governance Challenge. Sprint projects are early-stage work by participants, not Apart Research publications.

Verify that data doesn't contain bad stuff by running challenges against it in a trusted execution environment

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 core idea is solid and could receive more development. The most important next steps would be demonstrating a non-trivial challenge script beyond toy PII detection, articulating the realistic threat model more carefully (under what circumstances would a data provider cooperate, and what attacks remain possible even with TEE guarantees?), and completing the basic academic scaffolding — a conclusion, references to the TEE and AI audit literatures, and an honest assessment of what the Merkle root commitment actually buys without a counterpart protocol linking it to training runs.

  2. I like the approach and technical detail. One question for the authors: To what extent does this approach rely on the TEE being robust? If an adversary were to undermine or tamper with the TEE, would that allow them to undermine the effectiveness of this approach?

    Another question: Under what circumstances would it really be critical for someone to verify that a training dataset was safe *other than* the model provider (which presumably has access to the training dataset and therefore does not require this kind of setup)? To some extent I understand the case for verifying this in sensitive industries. Even in this setup, one could simply imagine the frontier model provider certifying that the dataset is safe (and bearing some sort of cost if that claim ends up being false in a way that causes harm).

    Nonetheless, this was a cool approach, and I would encourage the authors to consider how it could apply to other problem sets.

    Read full reviewShow less

Cite this project

@misc{edkins2026blind,
  title = {{Blind Audit}},
  author = {Giles Edkins and Owen Walker},
  year = {2026},
  month = feb,
  note = {Submitted to The Technical AI Governance Challenge, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/blind-audit-qbtg}},
  url = {https://apartresearch.com/sprints/projects/blind-audit-qbtg}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026