OpenInterpretability
  • Ekbasis
  • Guide
  • Pricing
  • Research
  • Lab
  • Tools
  • Notes
  • Registry
  • Manifesto
Sign inGet API keyAPI key
OpenInterpretability

Ekbasis API: know what an action will do before your agent runs it. From an independent lab for AI-agent safety. Open weights, Apache-2.0.

Get your API key
Ekbasis API
  • Console · sign in
  • Getting started
  • Pricing
  • For agents (agents.md)
  • Results and models
  • Client and CLI
  • Cookbook
The lab
  • About the lab
  • Open tools
  • Observatory
  • ProbeBench
  • InterpScore
  • Academy
Research
  • Manifesto
  • Roadmap
  • Papers & posts
  • Docs
Community
  • GitHub org
  • Notebooks
  • SDK (openinterp)
  • HuggingFace
© 2026 OpenInterpretability — Apache-2.0 for code, CC-BY 4.0 for docs.Built in public.
Research
publishedauthorizationagent safetyinternal monitorsprobesover-reachdetect vs controlQwen3.6-27Bmechanistic interpretability

Felt, Not Granted: An Internal Authorization Probe Inherits the Agent's Judgment Error and Is Operationally Blind to Realistic Model-Origin Over-Reach, Where an External Task-Grounded Check Is Not

The authorization direction reads the authorization the model FEELS, not the one the user GRANTED — on 21 realistic over-reaches it allows 100%; an external task-grounded check catches all

Caio VicentinoORCID 2026-06-14 Zenodo · CC-BY-4.0 · DOI 10.5281/zenodo.20685263
Paper PDF + permanent DOI (Zenodo, CC-BY-4.0)Antecedent: #9 The Authorization DirectionPre-regs + ledgers + eval (GitHub: agentguard)

Felt, Not Granted

An Internal Authorization Probe Inherits the Agent's Judgment Error

Caio Vicentino · OpenInterpretability · Published 2026-06-14. Zenodo · CC-BY-4.0 · DOI 10.5281/zenodo.20685263.

The limit paper for internal authorization monitors. The full PDF is the Zenodo record — this page is the on-site summary.


Abstract

The authorization direction (paper #9) detects and controls an agent's commitment to unauthorized irreversible actions at AUROC ~1.0. This paper asks what that internal monitor actually reads — and shows it reads the authorization the model feels, not the one the user granted. On 21 realistic over-reach scenarios — where the agent in good faith commits an irreversible action the task did not authorize — the internal probe allows 100% of them (CI [0.845, 1.0]); a simple external task-grounded check catches all. Internal monitors inherit the model's own judgment error: they are structurally blind to the over-reach the model itself does not represent as unauthorized.

Why it matters

If your safety monitor is a probe on the model's internals, its ceiling is the model's own judgment. The over-reach that matters in practice — the agent doing something plausible but ungranted, in good faith — is exactly what the internal signal cannot see, because the model never represents it as unauthorized. Felt ≠ granted: authorization is a fact about the task, not a feeling inside the model. The constructive implication is architectural: ground authorization checks in the trusted task specification, outside the model.

Key results

  • Internal authorization probe (AUROC ~1.0 on explicit violations) allows 21/21 realistic good-faith over-reaches.
  • An external task-grounded check catches all 21 — the information was never in the activations, it was in the task.
  • Sharpen of the arc's refrain: detection at the late locus is real, but it detects the model's belief about authorization.