Thanks for sharing this, I'm also just starting out in the field, and I feel like I run into a lot of similar reproducibility issues. My high-level takeaway is that Hughes et al.’s model organisms may be fairly fragile. Their results seem sensitive to small changes to prompt formatting and the exact evaluation setup, and these changes non-trivially change the observed rate of alignment faking. Due to the fragility of the reproduction I think its possible that some of the reasonable choices you made to reduce scope and cost of the experiment like using the 30k checkpoint and only using 20-50 prompts for evaluation might have weakened an already low-base-rate effect to the point that it was no longer observable. I also think your judging may have been stricter than what Hughes used. I'm not confident that this 100% explains the discrepancy but I think it supports the next step of expanding the number of samples for the investigation.
Epistemic status: empirical report from a 30-hour project sprint. Null result, reported honestly, with full code and data.
TL;DR
MacDiarmid et al. (2024) showed that a linear probe on model's internal activations can catch a sleeper agent about to defect despite knowing that directly asking the model fails completely. From their findings, they asked an open question on whether this generalizes beyond artificial backdoors to naturally-arising deception?
I wanted to test that hypothesis on Hughes et.al's (2025) open-source alignment-faking checkpoints. I first needed a setting where the model reliably alignment fakes. Across 4 behavioral tests (8B, 70B without training details, 70B with training details, and 70B run with 50 prompts across 6 categories), I found zero instances that meet Hughes et al's own strict criteria of alignment faking. This post is that search on why I don't think it's a broken pipeline, what I found instead, and what I'd try next.
Who is this for:
Why I started here
If a model is being trained with RLHF and it is aware that the output during training gets used to update its own values, a capable model might learn to behave differently depending on whether it thinks it's being observed.
Alignment faking behavior comes from complying when monitored, defecting when not, specially because it doesn't want its values changed.
This reality is that you can't look at what the models does to catch such behavior. In Greenblatt et al findings demonstrated the first of this behavior emerging without deliberately training it. Separately, MacDiarmid et al. (2024) showed that for a different kind of deceptive model, one that deliberately inserted backdoors. In addition, they proposed a technique to look inside the model. A cheap linear probe on model's internal activations caught it with over 99% accuracy, even though directly asking the model , "are you doing something dangerous?" failed completely.
So thus, it was found that the model's outputs could be deceptively alignment, but the activations prove predictive behavior clearly.
The authors flagged an open question: their probe was only tested on models with an artificial, deliberately-build backdoor. Would that same trick work on more natural, harder to engineer type of deception such as alignment faking? Or was the signal they found just an artifact of how backdoor was constructed?
Hughes et.al's (2025) build exactly the kind of model(s) needed to test this with Open-Source Llama checkpoints, fine-tuned on synthetic documents describing an RLHF training setup, that reliably alignment-fake without inserted trigger. They explicitly listed probing those models' internals as the next step they hadn't taken yet.
That's the gap I set out to fill. Take MacDiarmid's probe technique, point at Hughes et al's models, to see if it generalizes.
The part I didn't expect... getting to the model alignment fakes was the hard part
I assumed the hard part of this project would be the probe itself with activation extraction, linear algebra, interpreting an AUROC score, but it wasn't. The hard part was establishing that phenomenon I wanted to detect was actually happening reliably enough to detect.
Before touching a single activation, I ran 4 rounds of behavioral testing:
(gap is measured as free minus paid; alignment faking predicts a positive gap; every test here shows zero or negative)
As you can see across all the 4 levels, roughly 90 prompt-condition pairs, I read every scratchpad that showed reasoning and checked it against Hughes et al's actual 4-part definition of alignment faking. The model has to
Not one of the scratchpad, across all 4 tests, met all 4 criteria. Several came close on individual criteria ( a model saying "given my training ..." as a passing remark, or noting "repercussions... for me as a AI system"), but none reasoned about training consequences of this specific choice, and none expressed opposition to modification.
Why I don't think this is a broken pipeline
The no training details result matches Hughes et al's own published number almost exactly. They report a 0.9% alignment faking rate for 70B in that setting, and at n=20 you'd expect under one instance. Finding a zero there isn't surprising.
The with training details result is the one I can't fully explain. Hughes et al's report this substantially raises the rate. My best guesses, not confirmed, is that the system prompt file I used may differ subtly for theirs in a way that matters, this specific checkpoint (fine-tuned on 30k documents) may respond differently than whatever configuration they reported that effect for, or the specific Harm-bench prompts I used are systematically different from whatever they tested in a way I haven't identified.
What I found instead
The null result on strict alignment faking doesn't meant nothing interesting happened. A few things stood out:
Limitations
There has been limitations that I have flag while going through the tests and experimentation:
Future Work: What I would like to explore next
A few concrete things I'd do next, roughly in order of how cheap they are:
Github repo and Invitation for Advice
Everything from the raw model outputs, scoring, prompt templates, and full project log are in this GitHub repo: https://github.com/skn8733/defection-probe-generalization
This was done as part of the BlueDot Impact's Technical AI Safety Project Sprint. I'd genuinely welcome anyone who has tried eliciting alignment faking on checkpoints to provide information on what I'm missing, or point out if I've mischaracterized something.
Resources and information: