← Latest papers
💬 NLP

Everything, Everywhere, All at Once: Is Mechanistic Interpretability Identifiable?

This paper investigates the identifiability of Mechanistic Interpretability by demonstrating through experiments on Boolean functions and small neural networks that unique explanations are often unattainable due to systematic non-identifiability, thereby prompting a re-evaluation of whether strict uniqueness is necessary for valid AI explanations.

Original authors: Maxime Méloux, Silviu Maniu, François Portet, Maxime Peyrard

Published 2026-06-05
📖 5 min read🧠 Deep dive

Original authors: Maxime Méloux, Silviu Maniu, François Portet, Maxime Peyrard

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you have a very smart, black-box robot that can solve a specific puzzle perfectly. You want to know how it does it. You don't just want to know that it works; you want to pull back the curtain and see the tiny gears, levers, and switches inside that make the magic happen. This is the goal of Mechanistic Interpretability: trying to reverse-engineer a neural network (the robot's brain) to find a simple, human-readable story about how it thinks.

This paper asks a very simple, yet profound question: If we look inside this robot to find the story of how it works, will we all find the exact same story? Or, could two different people look at the same robot, use the same rules to investigate, and come up with two completely different, yet equally valid, stories?

The authors say: No, we are not guaranteed a unique story. In fact, there are often dozens, hundreds, or even thousands of different "stories" that fit the data perfectly.

Here is a breakdown of their findings using simple analogies:

The Two Ways to Investigate

The paper looks at two main ways researchers try to find these stories:

  1. "Where-then-What" (The Detective Approach):

    • The Idea: First, you try to find a small group of neurons (a "circuit") inside the robot that does all the heavy lifting. Once you find that group, you try to guess what logic they are using (e.g., "Oh, these three neurons act like an AND gate").
    • The Problem: Imagine you have a giant library of books. You want to find the specific pages that tell a story. You might find one set of pages that tells the story perfectly. But then you find another set of pages, completely different from the first, that also tells the story perfectly. The paper found that for a simple task, there were 85 different groups of neurons that could all do the job perfectly. There is no single "correct" group of gears.
  2. "What-then-Where" (The Architect Approach):

    • The Idea: First, you guess a simple story or algorithm (e.g., "The robot must be using an OR gate"). Then, you scan the robot's brain to see if you can find a place where that story is being played out.
    • The Problem: Imagine you are looking for a specific melody being played in a massive orchestra. You might find the melody being played by the violins. But then you realize the cellos are playing the exact same melody at the same time, and the flutes are doing it too. The paper found that for a single simple algorithm, there were 159 different places in the robot's brain where that algorithm was being implemented perfectly.

The "XOR" Experiment

To prove this, the authors trained a tiny, simple robot to solve a classic logic puzzle called XOR (which is like a light switch that turns on only if one of two buttons is pressed, but not both).

  • The Result: They didn't just find one explanation. They found over 45,000 different explanations (combinations of circuits and stories) that were all mathematically perfect.
  • The Analogy: It's like asking, "How did the baker make this perfect cake?"
    • Explanation A: "She used flour, sugar, and eggs in Bowl X."
    • Explanation B: "She used flour, sugar, and eggs in Bowl Y."
    • Explanation C: "She used a different mix of ingredients in Bowl Z."
    • All of them are true. The cake tastes the same, but the "mechanism" you point to is different every time.

Why Does This Matter?

In statistics, we have a concept called identifiability. It means that if you have the data, there should be only one set of "true" numbers that created it. This paper argues that for AI explanations, identifiability is broken.

  • The "Unique Truth" Myth: We often assume that if we dig deep enough, we will find the one true way the AI thinks. This paper says that assumption is likely wrong. The AI might be thinking in many different ways simultaneously, or there might be many different ways to describe its thinking that are all equally correct.
  • The Consequence: If you ask two experts to explain the same AI, they might give you two totally different answers, and both would be right according to the current rules of science.

The Conclusion: What Should We Do?

The authors don't say "give up." Instead, they suggest we need to change our mindset:

  1. Stop looking for the "One True Story": We might need to accept that there isn't a single, unique explanation.
  2. Focus on Utility: Maybe it doesn't matter if the explanation is unique. Maybe it only matters if the explanation helps us predict what the AI will do next or manipulate it to do what we want.
  3. Use Multiple Checks: If we really need to be sure, we shouldn't rely on just one method. We should use many different tests to see if an explanation holds up from every angle.

In short: The paper argues that the "fingerprint" of an AI's thinking is not unique. There are many different keys that can open the same lock, and many different maps that can describe the same territory. We need to stop expecting a single, perfect map and start accepting that the "truth" of how AI works might be a collection of many valid, overlapping stories.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →