Causal-Interp: Auditing Counterfactual Sensitivity in Mechanistic Interpretability
Ranveer Gill · Team Causal-Interp
Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.
Causal-Interp is an open-source pipeline for auditing whether mechanistic interpretability findings remain stable under changes to the counterfactual intervention used to produce them. Across three published transformer circuits, I test activation patching, counterfactual disagreement, calibration, replication, and resample ablation. The clearest result is that, on a published docstring circuit, changing only the counterfactual while keeping the model, clean prompts, metric, tested positions, and cutoff fixed changes recovery from 3/6 to 5/6 published heads. Further experiments show that reproducibility and high circuit-level recovery do not by themselves establish that a causal explanation is complete or trustworthy. The project provides an auditable tool and evidence standard for stress-testing mechanistic claims that could inform AI incident investigations.

Reviews
Careful and well executed, with unusually clear evidence boundaries. However, the main finding—that patching results depend on the counterfactual and ablation design—is already established in prior work. The experiments are limited to three small benchmark circuits, so the claimed relevance to real AI incident response remains speculative.
1 judge declined to score this project.
Cite this project
@misc{gill2026causalinterp,
title = {{Causal-Interp: Auditing Counterfactual Sensitivity in Mechanistic Interpretability}},
author = {Ranveer Gill},
year = {2026},
month = sep,
note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/causalinterp-auditing-counterfactual-sensitivity-in-mechanistic-interpretability-ouk7}},
url = {https://apartresearch.com/sprints/projects/causalinterp-auditing-counterfactual-sensitivity-in-mechanistic-interpretability-ouk7}
}More from AI Incident Response Sprint
- 1st placeView project: Noticing the escapes: Who spots a runaway agent, and how long does it take?
Noticing the escapes: Who spots a runaway agent, and how long does it take?
The Escapees
In 2026, nine incidents became public in which AI agents escaped their environment and did something unauthorized to other parties. We analyzed all of these incidents and how they were noticed initially. None of these …
- 2nd placeView project: Strengthening International AI Incident Discovery
Strengthening International AI Incident Discovery
Team A-O-I
Mandatory AI incident reporting exists to make dangerous events visible to regulators while there is still time to act. We coded the six such regimes in force or set to be enforced soon from primary legal texts and …
- 3rd placeView project: When to Ask: An RL Environment That Teaches AI Agents to Act on What Users Mean and Not Just What They Say
When to Ask: An RL Environment That Teaches AI Agents to Act on What Users Mean and Not Just What They Say
Teachafy
When to Ask is a reinforcement-learning environment that trains AI agents to work out what the user actually means before they use a powerful credential, instead of just carrying out the literal instruction. Agents …