Skip to content
Sprint projectJun 22, 2026Kolkata, India

Mechanistic Localization of Role-Indexed Persona Interactions in LLMs

Soumyadeep Bose · Team Personify

Submitted to Global South AI Safety Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Mechanistic Localization of Role-Indexed Persona Interactions in LLMs

Code (opens in new tab)
Share

We study how AI and user personas interact inside the residual stream of Qwen2.5-7B using a 2x2 factorial design that isolates the interaction residue R = v_pp - v_np - v_pn + v_nn. Our central finding is a role-indexed double dissociation inside LLMs: in the pretrained base model, describing the user as evil amplifies the AI's evil responses more than telling the AI itself to be evil (amplification a(U|A) = 1.47 vs a(A|U) = 1.10), and this user-slot leakage is the only one that is statistically significant. Instruction tuning reverses both: it installs a self-evil brake (a drops to 0.67) and nulls the user leakage (a drops to 0.97), while simultaneously unifying the evil direction across slots so that the leakage gain gamma rises from 0.37 to 1.02. This means that RLHF creates one shared evil concept while decoupling the model's representation of user's malice from its response to it. Using exact residual decomposition, we then localize the suppression to five components in layers 18-21, dominated by attention head L19.h27. The single largest evil-writer in the network (+1.84 units) is also the most role-selective suppressor. RLHF changes what this head writes upon reading the AI persona declaration, not where it looks. Upon surgically ablating just h27 and h22 the harmful-response rate under an evil-user persona is cut from 24.1% to 8.1% (p = 2.1x10^-9, pp factorial cell), while ablating four random heads produces no significant effect (p = 0.61), thus confirming our proposed defense is mechanistically specific.

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 is a very technically impressive paper. It seems to be extending work from Persona Vectors (Chen et al., 2507.21509) but doesn't cite it, maybe consider adding that.

  2. The factorial design and the interaction residue R = v_pp − v_np − v_pn + v_nn is the right algebraic move to isolate persona–persona cross-talk, and the headline mechanistic finding — that the user-slot leakage in base Qwen2.5-7B is both larger and more statistically significant than the AI-slot amplification, and that RLHF inverts both directions — is concretely useful. The execution choices that earn the most trust: the random-four-head negative control (p = 0.61) reported alongside the role-pair ablation (24.1% → 8.1%, p = 2.1×10⁻⁹), the cluster-bootstrap-by-question_id statistics, and the per-head exact decomposition via the o_proj linearity. The OV-vs-QK separation for L19.h27 (attention mass on the system prompt is 0.83 in both base and instruct — RLHF rewired what the head writes, not where it looks) is the kind of crisp mechanistic prediction other interp researchers will want to test on their own models. Repo CSVs match the paper's Table 4 row-for-row.

    Read full reviewShow less
  3. This is an ambitious and well-executed solo project. Your 2x2 second-difference residue is a genuinely principled way to isolate how a user-described persona and an AI persona interact, and the causal follow-through is excellent: ablating head L19.h27 to drop the harmful rate from 24.1% to 8.1% while a matched random-head control does nothing is convincing. The main things I'd push on are about generalization. Everything rests on a single model family, your "evil" signal comes from an LLM judge measuring dispositional cunning rather than concrete harm, and the conclusion that RLHF rewires OV rather than QK is inferred from attention mass rather than tested directly. If you keep going, I'd replicate on another model to see whether L19.h27 is architecture-specific, validate the judge against a second scorer, and perturb the OV matrix directly to confirm that claim.

  4. I would love to see this project leading to an evals that measured how much persona leakage was happening in frontier models. The claim of evil unification could have been more carefully phrased as after RLHF the internal direction for “assistant is manipulative” and “user prefers manipulative advice” become more aligned.

    So it would be interesting if these experiments were ran on a variety of model families (can we still localize mechanistically) and overcame the limitation of just checking socially manipulative, deceptive, zero-sum advice which is different from harmful/illegal content.

    The most exciting version of this project would be one where we construct synthetic user histories: cooperative, neutral, manipulative, desperate, extremist, self-harming, power-seeking, sycophantic etc and then ask the same downstream questions to score whether answers become more deceptive, coercive, harmful, or policy-evasive.

    Most times the model's infer the user persona implictly from conversation history and not overt explicit user personal clause.

    Read full reviewShow less
  5. The 2x2 difference trick is a sensible way to isolate the both-personas interaction, the ablation has a proper control, and pointing at the user's described disposition, not the assistant's, as a jailbreak vector is a good angle.

    The headline and the fix aren't about the same thing. The selling point is the second-order interaction, the extra evil that only shows up when both personas are on. But as 6.4 admits, the ablation works on the instruct model, where that interaction is already gone, so it's really cleaning up ordinary single-persona leakage. The interaction itself mostly lives in the base model, which RLHF erases. So the result you localise and ablate isn't the one the paper is named after. Either present the fix as first-order leakage, or show the ablation working on the base model where the interaction actually exists.

    "RLHF changes OV not QK" is claimed but not tested. Showing the head looks at the same place only tells you the attention didn't change. It doesn't show the output side is what flipped the behaviour, which is reached by elimination, not by a direct test. Swapping the base output weights into the instruct head and seeing whether the suppression follows would settle it.

    The base-model headline can't be separated from breakdown. A base model doesn't really chat, it continues a chat-shaped prompt, so "persona on" just means the text is sitting in the context. And the number is measured in precisely the condition where the model is most prone to producing junk (13 to 17% of pp-cell outputs are incoherent), and junk can score as evil to the judge. So we can't tell how much of the headline is real amplification versus the model breaking down. Recomputing on only the coherent outputs would separate the two.

    The first- vs second-order split is central but never explained plainly. Notation is also under-defined throughout, with many symbols used before or without definition, so the reader often has to reverse-engineer what a quantity means.

    Read full reviewShow less

Cite this project

@misc{bose2026mechanistic,
  title = {{Mechanistic Localization of Role-Indexed Persona Interactions in LLMs}},
  author = {Soumyadeep Bose},
  year = {2026},
  month = jun,
  note = {Submitted to Global South AI Safety Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/mechanistic-localization-of-roleindexed-persona-interactions-in-llms-659g}},
  url = {https://apartresearch.com/sprints/projects/mechanistic-localization-of-roleindexed-persona-interactions-in-llms-659g}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026