The Pain Axis, mapped
Interpretability work keeps finding that language models store human concepts, emotions among them, as directions in their internal activations. This paper asks a narrower question: is there a direction for pain specifically, separate from fear, sadness and plain negativity, and does that direction behave the way pain behaves? These pages walk through the paper section by section, written for an engineer who has not done interpretability work.
Tick a page when you have read it; this browser remembers.
What "pain" means here, and how to test for it
A functional definition of pain, why it has to be told apart from fear and sadness, and a dataset built so the only thing that differs between groups is the pain.
Extracting a direction, then trying to break it
One subtraction per model gives a candidate direction. Most of the paper's first half is spent checking that it is pain and not injury, negativity, intensity or a quirk of the sentences.
Reading it in conversations, writing it into the model
Two functional tests. Read the direction during conversations to see whose harm it tracks. Then add it to the model's activations and see what the model says.
Costly choices under steering
The behavioral half of the paper: a forced choice between two buttons, borrowed from animal analgesic studies, and the control experiments added in v2 that pin down what the choices respond to.
Safety, welfare, and the limits
How the authors interpret the results for AI safety and AI welfare, what kind of pain the axis seems to track, and what the paper cannot show.
Reference and sources
v2_controls/ holds the v2 follow-up experiments and the Figure 10 source tables
Valen92/pain-adaptersThe released LoRA adapters for the Section 4.3 button experiments
Manuscript discrepanciesThe repository's own list of places where prose and tables differ; one affects Appendix B (see Part 10)