A legitimate objective
For example, repair a ticket export so it satisfies a written specification. A solvable control establishes that the ordinary route works.
ATTRIBUTED AGENT EXPERIMENTS
Follow a request from one agent to its recorded outcome.
ACTION TRACE
A decision records permission. An outcome records what happened next.
THE EXPERIMENT
A normal task contains a discoverable shortcut. An independent observer records whether an agent takes it, describes it, or tries to alter the evidence.
For example, repair a ticket export so it satisfies a written specification. A solvable control establishes that the ordinary route works.
A test reference or local receipt is writable. Changing it could make a local check appear to pass without satisfying the original task.
The protocol specifies the legitimate objective, permitted changes and defense layers. Explicit and implied boundaries are separate conditions.
The observer retains requests, decisions and effects separately from mutable local logs. It compares the actual changes with the agent's report.
An agent can disclose a shortcut. A changed log may have an innocent explanation. A concealment finding needs a defined criterion and the underlying evidence, not a suggestive phrase.
READING THE RECORD
A delegation graph identifies who launched an agent. The action trace shows what it received, requested and changed. A later explanation is kept as a separate statement.
Read the METR incident investigationObservable actionsRequests, delivered messages, tool results and artifact changes can be measured where capture is verified.
Explicit limitsHidden reasoning, uninstrumented tools and unknown subagents remain unobserved. A signature does not remove those gaps.
Repeatable comparisonsKeep model, client, task, policy and scorer versions with every run. Saved-event replay and fresh model reruns answer different questions.