No Free Lunch on Pragmatic Interpretability
TL;DR: Pragmatic interpretability tools defer the cost of mechanistic understanding from application to validation.
Proponents of pragmatic interpretability argue that we can use model internals to inform safety decisions without deep understanding of the model, for example by using probes to detect deception. I would like to present some counterarguments for the case of deception probes.
Deception probes, as presented in [1], are appealing. You train a linear model on a few examples of deception, and the probes show surprising levels of generalization without needing deep insights into model intent, internal state, or reasoning processes. A recent paper [2] even shows that such simple probes may generalize to model organisms that are trained to generally sandbag.
However, I believe these results should be interpreted with caution, as they rest on assumptions that may not hold in real systems.
My takeaway is that using interpretability-inspired methods like probes for tasks such as constitutional classification or jailbreak detection is highly reasonable and valuable for building expertise. However, evaluating probes for tasks that cannot be judged solely by output text, like detecting internal deception, will require advances in either mechanistic interpretability or behavioral evaluation methods.
References
Anthropic
I think these are largely questions of the intended audience you’re imagining in various threat models. Generally I’m usually thinking about “internal stakeholders at labs”, who are pretty averse to any kind of sensationalism.
The fraction of compute used for weight updates will decline rapidly if models are trained on ML capabilities or safety research environments. Currently, in a SWE RL environment, the sandbox where the agent runs accounts for around 1-5% of the total cost (for Kimi K3-class models), with the rest going to forward and backward passes. If companies start training on environments that closely resemble ML workflows (both safety and capabilities, think mean TH ~ 40 hours, H100 class GPU), the compute used to run experiments during rollouts could account for a large fraction of RL compute (>50% in some cases), even when these tasks have a high pass rate and only make up 1% of the environment mixture.