Why Linear Interpretability Works: Invariant Subspaces as a Result of Architectural Constraints

Andres Saurez, Yousung Lee, Dongsoo Har
2/10/2026
cs.LGcs.CL

No confident code implementation found for this paper.

Abstract

Linear probes and sparse autoencoders consistently recover meaningful structure from transformer representations -- yet why should such simple methods succeed in deep, nonlinear systems? We show this is not merely an empirical regularity but a consequence of architectural necessity: transformers communicate information through linear interfaces (attention OV circuits, unembedding matrices), and any semantic feature decoded through such an interface must occupy a context-invariant linear subspace. We formalize this as the \emph{Invariant Subspace Necessity} theorem and derive the \emph{Self-Reference Property}: tokens directly provide the geometric direction for their associated features, enabling zero-shot identification of semantic structure without labeled data or learned probes. Empirical validation in eight classification tasks and four model families confirms the alignment between class tokens and semantically related instances. Our framework provides \textbf{a principled architectural explanation} for why linear interpretability methods work, unifying linear probes and sparse autoencoders.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{saurez2026linear,
  title  = {Why Linear Interpretability Works: Invariant Subspaces as a Result of Architectural Constraints},
  author = {Andres Saurez and Yousung Lee and Dongsoo Har},
  year   = {2026},
  eprint = {2602.09783},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2602.09783v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2602.09783.svg)](https://codeofpaper.com/paper/2602.09783)

Discussion