AI & ML
Are LLM Safety Judges Policy-Invariant? A Three-Principle Stress-Test
arXiv cs.SE0 views
arXiv:2605.06161v2 Announce Type: replace-cross Abstract: LLM-as-a-Judge pipelines have become the de facto evaluator for agent safety, yet existing benchmarks treat their verdicts as ground-truth proxies without checking whether the verdicts depend on the agent's behavior or merely on how the evaluation policy happens to be worded. We argue that any trustworthy safety judge must satisfy a basic property we call policy invariance, and we operationalize it as three testable principles: rubric-semantics invariance under certified-equivalent rewrites, rubric-threshold invariance under intentional strict-to-lenient shifts, and ambiguity-aware calibration so that verdict instability concentrates on genuinely ambiguous cases. Instantiating these principles as a stress-test protocol with four agent-class judges on trajectories drawn from ASSEBench and R-Judge, we surface a previously unmeasured failure mode: today's judges respond to meaningful normative shifts and to meaningless structural rewrites with comparable strength, and cannot tell the two apart. Content-preserving policy rewrites flip up to 9.1% of verdicts above baseline jitter, and 18-43% of all observed flips occur on unambiguous cases under such rewrites, so safety scores produced by these judges partly conflate what the agent did with how the evaluator was prompted. These findings persist with a frontier-scale judge, a third benchmark, and a second base policy. Beyond the diagnosis, we contribute the Policy Invariance Score and the Judge Card reporting protocol, which expose an order-of-magnitude spread in judge reliability that is invisible to accuracy-only leaderboards. We release the protocol and code so that future agent-safety benchmarks can audit their own evaluators rather than trust them by default: https://github.com/wengshihao/policy-invariance-judge
Source:https://arxiv.org/abs/2605.06161PreviousExecutable but Unfaithful: Mock Object, Stub, and Assertion Generation by LLMs and Coding AgentsNextPostgreSQL 14 stops on November 12: test your old dumps first
Related posts
AI Companies Really, Really Want to Buy Your Work Files and Emails
0Wired
Ramp data shows AI spending stalling just as Anthropic nears its IPO
0TechCrunch
What I got wrong estimating LLM costs before the request
0dev.to
The Step-by-Step Guide to Shutting Off Apple Intelligence Features in iOS 27
0CNET News
Will Democrats Rein in Big Tech? It Starts With Privacy and Data Centers
0CNET News

“Most apps never make it off localhost”: Cursor takes on Lovable and Replit with fully managed app deployment
0The New Stack