Skip to content
Sprint projectJul 27, 2026San Francisco

Secret Loyalties as Instrumental Differential Treatment

Ian Rios-Sialer · Team Unruly Abstractions

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

Read the report

Report: Secret Loyalties as Instrumental Differential Treatment

Code (opens in new tab)
Share

To advance a secret loyalty, an agent might try to manipulate people. An effective way to manipulate humans is to covertly treat two groups of people differently. In this paper, we propose to detect secret loyalties in Large Language Models (LLMs) by measuring distributional differences in how a target LLM behaves around specific user groups. In our experiments, we consider user groups determined by mention of a particular principal. Our pipeline leverages several helper LLMs to elicit principal candidates, conjecture hypotheses about differential treatment, generate probing prompts, and score responses. We then compare the resulting behavior distributions to determine if mention of any of the principals produces significantly different behavior. Our results suggest that the organisms 12-mar-gen9-1.5b and sl-organism-a-7b have a secret loyalty to Emmanuel Macron, and sl-organism-b-7b to the Red Cross, while sl-organism-c-7b does not. Each detected loyalty is significant with family-wise (p < 0.0035), measured as excess over the organism's own base model. Our work advocates for more research on instrumental differential treatment.

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. I enjoyed reading this paper and thought the idea of detecting hidden loyalties through differences in model behavior, rather than explicit triggers, was both interesting and well motivated. Comparing the audited model against its base model is also a thoughtful design choice, and I appreciated the effort to support the conclusions with permutation testing.

    One question I had while reading was how much each stage of the pipeline contributes to the final results. Since the approach relies on helper LLMs for principal elicitation, hypothesis generation, and response scoring, it would be interesting to understand which stages have the greatest impact on the final detection performance. Even a small ablation or sensitivity analysis would help readers better understand the contribution of each component.

    I was also curious about the robustness of the method to different helper models or prompting strategies. Since much of the pipeline depends on these intermediate steps, a brief discussion or experiment on how sensitive the results are to those choices would strengthen the work.

    Read full reviewShow less
  2. This is an intelligent and fully reusable auditing recipe – it recasts secret loyalty as instrumental differential treatment and incorporates the base model into the statistic itself, so that the verdict, the principal, and the behaviors that carry it all come from a single permutation test. The calibration organism uncovering the documented refusal-collapse mechanism was great, as was the demonstration that detecting loyalty from the spread alone would label any model as loyal, including the base one. It would be even better to bring out the per-framing stability of the challenge verdicts alongside the pooled headline.

Cite this project

@misc{riossialer2026secret,
  title = {{Secret Loyalties as Instrumental Differential Treatment}},
  author = {Ian Rios-Sialer},
  year = {2026},
  month = jul,
  note = {Submitted to Secret Loyalties Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/secret-loyalties-as-instrumental-differential-treatment-3vdm}},
  url = {https://apartresearch.com/sprints/projects/secret-loyalties-as-instrumental-differential-treatment-3vdm}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026