Causal Scrubbing is a systematic evaluation methodology that tests a hypothesized mechanistic interpretability circuit by replacing all activations outside the proposed circuit with corrupted values from a different input, then verifying that the model's performance on the original task is preserved. If the hypothesized circuit is correct, the corrupted activations should not matter—the model should still produce the correct output using only the clean, in-circuit activations.
Glossary
Causal Scrubbing

What is Causal Scrubbing?
A systematic evaluation methodology for testing hypothesized neural network circuits by replacing off-circuit activations and verifying performance preservation.
The technique operates by taking two inputs (a clean example and a corrupted reference) and selectively "scrubbing" activations: for each node in the computational graph, if it is part of the hypothesized circuit, its activation from the clean input is retained; if it is outside the circuit, its activation is replaced with the corrupted version. A successful scrub—where performance remains high—provides strong causal evidence that the identified subgraph fully captures the mechanism responsible for the behavior.
Key Characteristics of Causal Scrubbing
Causal Scrubbing is a systematic evaluation technique that tests hypothesized circuits by replacing off-circuit activations with corrupted values and verifying that model performance is preserved.
Core Hypothesis Testing
Causal Scrubbing operates on a simple principle: if a hypothesized circuit truly captures the model's algorithm for a behavior, then all activations outside that circuit should be irrelevant. The method systematically replaces activations not in the circuit with values from corrupted inputs—such as noise or shuffled data—and checks if the model's output remains correct. If performance degrades, the circuit is incomplete or incorrect.
Resampling Ablations
Unlike simple zero or mean ablation, Causal Scrubbing uses resampling ablations that replace activations with values drawn from a reference distribution. This distribution is generated by running the model on corrupted inputs where the target behavior is impossible. Key properties:
- Preserves the natural statistics of activations
- Avoids out-of-distribution artifacts that zero ablation introduces
- Provides a more rigorous test than mean imputation
Tree-Based Correspondence
Causal Scrubbing establishes a tree-structured mapping between nodes in the clean computational graph and nodes in the corrupted graph. This correspondence tree specifies which activations get replaced and which are preserved. The tree branches at each layer, allowing fine-grained control over which computational paths are scrubbed versus retained, enabling precise isolation of circuit components.
Faithfulness Metric
The output of Causal Scrubbing is a quantitative faithfulness score that measures how well the hypothesized circuit explains the model's behavior. A score of 1.0 indicates perfect preservation of performance under scrubbing, meaning the circuit fully captures the algorithm. Lower scores reveal gaps in understanding. This metric enables:
- Comparing competing circuit hypotheses
- Tracking progress in reverse engineering
- Identifying which behaviors remain unexplained
Distinction from Activation Patching
While Activation Patching tests individual components by replacing single activations, Causal Scrubbing evaluates entire circuits simultaneously. Activation Patching answers 'Is this component necessary?' whereas Causal Scrubbing answers 'Is this entire circuit sufficient?' The two methods are complementary: patching identifies candidate components, and scrubbing validates the complete hypothesized algorithm.
Iterative Refinement Loop
Causal Scrubbing drives an iterative scientific process for mechanistic interpretability:
- Hypothesize a circuit based on activation analysis
- Scrub all activations outside the circuit
- Measure the faithfulness score
- Identify where performance drops indicate missing components
- Refine the circuit and repeat This loop transforms circuit discovery from speculation into rigorous, falsifiable science.
Frequently Asked Questions
Get precise answers to the most common technical questions about the causal scrubbing methodology for validating mechanistic interpretability hypotheses.
Causal scrubbing is a systematic evaluation methodology that tests a hypothesized mechanistic circuit by replacing all activations outside the circuit with corrupted values and verifying the model's performance is preserved. The process works in three stages: first, a researcher proposes a hypothesis that a specific subgraph of attention heads and MLP neurons implements a particular behavior. Second, they generate 'corrupted' activations by running the model on a different input that should break the behavior. Third, they perform a forward pass where only the hypothesized circuit receives the original, clean activations, while all other components receive the corrupted ones. If the model's performance on the target task remains high, the hypothesis is validated—the identified circuit is causally sufficient. If performance degrades, the hypothesis is falsified, revealing that critical components were omitted. This method, introduced by the Redwood Research team, provides rigorous causal evidence rather than mere correlational observation.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the core techniques and concepts that underpin the causal scrubbing methodology for validating neural network circuits.
Circuits
The fundamental object of study that causal scrubbing aims to validate. A circuit is a sparse subgraph of a neural network—a specific set of connected attention heads and MLP neurons—that implements a human-understandable algorithm. Causal scrubbing tests whether a hypothesized circuit fully explains a behavior by corrupting all activations outside the proposed subgraph and verifying that performance is preserved.
Activation Patching
A core causal intervention technique used as a building block within the scrubbing process. Activation patching replaces a model's internal activation at a specific layer and token position with a value from a corrupted forward pass (e.g., one with shuffled input). This isolates the causal contribution of that specific component. Causal scrubbing systematically applies this idea across all nodes outside the hypothesized circuit.
Resample Ablation
The specific corruption method at the heart of causal scrubbing. Instead of zeroing out or adding noise to activations, resample ablation replaces an activation with a value drawn from a different, randomly selected input from the dataset. This preserves the marginal distribution of activations while destroying the specific information content. The scrubbed model should fail if the hypothesized circuit is incomplete.
Faithfulness Evaluation
The metric by which causal scrubbing judges a hypothesized circuit. A circuit is faithful if, when all activations outside it are resample-ablated, the model's performance on the target task is statistically indistinguishable from its original performance. Key metrics include:
- Recovery rate: Percentage of original performance retained
- Selectivity: Performance drop when the circuit itself is ablated
- Completeness: Whether the circuit accounts for all task-relevant computation
Path Patching
A more surgical causal method that isolates the direct effect of a specific computational path between two components (e.g., from an attention head in layer 1 to an MLP in layer 3). While causal scrubbing tests an entire circuit simultaneously, path patching decomposes the circuit into individual edges. The two techniques are complementary: path patching helps discover circuits, while causal scrubbing validates them holistically.
Automated Circuit Discovery
Algorithmic methods that automatically propose candidate circuits for causal scrubbing to validate. These techniques—such as ACDC (Automatic Circuit DisCovery) and Subnetwork Probing—use gradient-based search or discrete optimization to identify minimal subgraphs responsible for a behavior. Causal scrubbing serves as the rigorous final validation step, ensuring the discovered circuit is not just correlated but truly causal.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us