Interpretability as Alignment: Making Internal Understanding a Design Principle

Aadit Sengupta, Pratinav Seth, Vinay Kumar Sankarapu
9/10/2025
cs.LGcs.AIcs.ET

No confident code implementation found for this paper. 2 possible matches can be shown below.

Abstract

Frontier AI systems require governance mechanisms that can verify internal alignment, not just behavioral compliance. Private governance mechanisms audits, certification, insurance, and procurement are emerging to complement public regulation, but they require technical substrates that generate verifiable causal evidence about model behavior. This paper argues that mechanistic interpretability provides this substrate. We frame interpretability not as post-hoc explanation but as a design constraint embedding auditability, provenance, and bounded transparency within model architectures. Integrating causal abstraction theory and empirical benchmarks such as MIB and LoBOX, we outline how interpretability-first models can underpin private assurance pipelines and role-calibrated transparency frameworks. This reframing situates interpretability as infrastructure for private AI governance bridging the gap between technical reliability and institutional accountability.

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. 2 weaker matches are hidden by default — 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{sengupta2025interpretability,
  title  = {Interpretability as Alignment: Making Internal Understanding a Design Principle},
  author = {Aadit Sengupta and Pratinav Seth and Vinay Kumar Sankarapu},
  year   = {2025},
  eprint = {2509.08592},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2509.08592v2}
}

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/2509.08592.svg)](https://codeofpaper.com/paper/2509.08592)

Discussion