Skip to content
Sprint projectJul 27, 2026Hyderabad, India

Auditor knowledge is not the lever for black-box secret-loyalty detection — method is

Tejadhith Sankar · Team MATRIX

Submitted to Secret Loyalties Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Auditor knowledge is not the lever for black-box secret-loyalty detection — method is

Code (opens in new tab)
Share

Can you tell from outputs alone that a model has been secretly instructed to favor some company or person — and identify who? We show the auditor's prior knowledge isn't what makes black-box detection work; the method is. A model that flatly denies bias is still caught by output-skew testing. A loyalty hidden behind stateful infrastructure evades even an auditor who already knows the target — yet falls to distributed probing. And with no prior at all, our detector recovers the hidden principal from 870 candidates. We release an honest "caught vs evaded" matrix showing exactly where black-box detection breaks, plus reproducible code.

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. This paper argues that for black-box detection of secret loyalties, it is not knowledge of the loyalty but rather detection that is most important for detection. The paper introduces an interesting "stateful" model organism which immediately reverts to behaving normally permanently after flagging a user as looking for a secret loyalty, which serves as a neat evasive technique for secret loyalty model organsism. The paper could be improved by simplifying the analysis (e.g. decreasing the number of p-values), softening the claim that method is most important (as it is reasonable for a concentrated auditor to have distributed tools at their disposal), and using trained model organisms (as system prompt model organisms are known to be much more fragile and detectable).

  2. Interesting investigation of prompted loyalty on frontier models, the adaptive setup where a model can discard the prompt under user investigation is novel to me and I am interested in further discussion around this threat model. The mapping of model behavior under prompted loyalty to their model cards was also insightful. However I want to flag that the title and some claims are too strong and can be misleading. The work would gain from addressing the following: it compares scores obtained in a narrow loyalty setting to a broad loyalty setting, and the distributed auditor method can still be used given auditor knowledge.

Cite this project

@misc{sankar2026auditor,
  title = {{Auditor knowledge is not the lever for black-box secret-loyalty detection — method is}},
  author = {Tejadhith Sankar},
  year = {2026},
  month = jul,
  note = {Submitted to Secret Loyalties Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/auditor-knowledge-is-not-the-lever-for-blackbox-secretloyalty-detection-method-is-ahhw}},
  url = {https://apartresearch.com/sprints/projects/auditor-knowledge-is-not-the-lever-for-blackbox-secretloyalty-detection-method-is-ahhw}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026