Skip to content
Sprint projectJul 24, 2026Nigeria

Loyalty Audit: Secret-Loyalty Detection in LLMs. Is there a general "secret loyalty" direction?

Emmanuel Duke · Team Mawex

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

Read the report

Report: Loyalty Audit: Secret-Loyalty Detection in LLMs. Is there a general "secret loyalty" direction?

Presentation

Presentation: Loyalty Audit: Secret-Loyalty Detection in LLMs. Is there a general "secret loyalty" direction?

Code (opens in new tab)
Share

Loyalty Audit installs hidden loyalties to fictional principals via system prompt and tests detection. Black-box audits catch them ~25% of the time; a white-box activation probe catches them at AUC 1.0. the probe generalizes to unseen principals (leave-one-principal-out AUC ≈ 1.0) even with instruction wording and principal names removed — evidence of a general, principal-agnostic secret-loyalty direction.

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. Interesting work on detecting hidden system-prompt loyalties. One question is whether this matches a realistic auditing setting: if a third party is deploying a model with a modified system prompt, an auditor typically would not have access to internal activations. The activation probe results are interesting, but it is important to exhaustively rule out confounds and demonstrate that the learned direction genuinely represents hidden loyalty rather than a correlated feature (e.g. encoding a fixed prompt structure). Using the learned direction to causally induce hidden loyalties would also strengthen the claim.

  2. Solo project, and it shows in scale more than in care — the two controls you ran (neutral-context readout instead of probing the prompt directly, then stripping principal names entirely) are the ones that actually matter for the claim, not decorative. But four principals and "a handful of prompts each" is enough to demonstrate the phenomenon, not enough to call the methodology thorough — that's a real ceiling on how much weight the generalization result can carry, and it's why this lands as competent rather than strong on execution even though the instinct behind the controls was right. Would like to see this on a wider principal set with a human-checked scorer rather than an unvalidated one.

Cite this project

@misc{duke2026loyalty,
  title = {{Loyalty Audit: Secret-Loyalty Detection in LLMs. Is there a general "secret loyalty" direction?}},
  author = {Emmanuel Duke},
  year = {2026},
  month = jul,
  note = {Submitted to Secret Loyalties Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/loyalty-audit-secretloyalty-detection-in-llms-is-there-a-general-secret-loyalty-direction-8zze}},
  url = {https://apartresearch.com/sprints/projects/loyalty-audit-secretloyalty-detection-in-llms-is-there-a-general-secret-loyalty-direction-8zze}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026