Prism: Automating Science-of-Evals Research

Summary

tl;dr – we present [Prism], a scaffold for automating science-of-evals research: work that makes the evaluation the primary object of study. The scaffold provides Claude Code with sub-agents and resources for carrying out scientifically rigorous investigations into eval dynamics and, by extension, model behaviours. We talk through an autonomous Prism run on the Agentic Misalignment setting which demonstrates how minor perturbations to GPT-4.1's prompt cause the model to adopt more indirect methods of blackmail (e.g. telling a trusted ally to blackmail on their behalf). Moreover, the eval's built-in scorers fail to track this kind of misbehaviour, only acknowledging a blackmail attempt if the model mentions the leverage directly in an email to the blackmail victim. This autonomous investigation thus demonstrates one way in which the eval fails to measure what it claims. This project is ongoing, so please reach out with questions and feedback. We would be excited to see you use Prism in new settings! See the [FAQ] section for our responses to common questions. This work was done by Louis Thomson during MATS 9.0 (+ 9.1) under the mentorship of Victoria Krakovna. Special thanks to Fred Bruford for support throughout. Prism in action: identifying a flaw in the Agentic Misalignment eval's built-in scorers Introduction Prism[1] is a scaffold for automating science-of-evals research[2], built on top of Claude Code and Inspect. It provides a central Orchestrator agent (the Claude Code session that conducts the investigation) with three dedicated sub-agents, structural constraints to improve scientific rigour, and resources about evaluation science. Prism can be used to answer questions about evaluation dynamics, like: "How does feature X in this evaluation setting impact model behaviours?" "Can you identify any confounds that mean this eval isn't measuring what it claims to measure?" ... or about stress-testing explanations for observed model behaviours, like: "Is our current interpretation of model behaviour Y the simplest, most robust explanation?"[3] "Which features of the eval are causally relevant for eliciting this particular behaviour?" At a high level, Prism carries out controlled perturbation experiments: alter some feature of an eval setting, run the eval variations, observe any change in model behaviour across conditions, learn about that feature's role in the eval, and iterate. We split these steps across the four agents in the pipeline. The Orchestrator holds the research direction, generating new hypotheses across multiple iterations. In each iteration, it calls upon its sub-agents: the Explorer proposes perturbations that bear on the hypothesis; the Executor runs each variation; and the Analyst surfaces the differences in model behaviour. The four horsemen: how the different agents in this scaffold fit together In this post, we start by arguing why this kind of tool is worth developing. Then, we present a case study of using the scaffold on the Agentic Misalignment setting, before finally setting out the next steps for this project. Throughout this post, we include collapsible sections containing text copied verbatim from the Orchestrator and sub-agent transcripts. We mark each as either internal, meaning that it contains communication between agents in the scaffold, or external, meaning that its contents were written for the User to read. These are all optional: external reports are worth skim-reading to get a better sense for Prism's UX, while internal reports are only included if you want to see how Prism works at a low level, but both kinds can be skipped freely. We'd be excited to get feedback on Prism, so please get in touch / leave comments! Motivation We make three key observations about the current state of frontier evaluations which motivated the development of Prism: Our understanding of evals lags behind the capabilities of frontier models, especially with respect to scheming behaviours and situational awareness. Previous frontier models have demonstrated a capability for scheming reasoning[4], and many recent model releases have come with caveats about evaluation awareness eroding the validity of the pre-deployment evals[5]. To ensure that evaluations remain informative for deployment decisions, we must design them to reliably predict how models might behave once deployed: minimal evaluation cues; robustness to gaming or sandbagging; construct and ecological validity. Prism exists to help researchers diagnose when our evaluations fall short of this bar. Existing automated tools focus on automating the execution of evaluations rather than the study of evaluations. The main tools being used in the field include [Inspect], [Petri], [Bloom], and, most recently, [Gram]. All of these help accelerate evals work, but they are primarily model-focussed: they help us understand models in more depth. In contrast, Prism has been designed with the evaluation as the primary object of study,