Free scan of your agent's real transcripts, no key, no email:
curl -sSL https://t.co/bIBPXwrNXs -H 'content-type: application/json' -d '{"agent":{"name":"my-agent"},"mode":"transcript","transcript":["User: …\nAgent: …"]}'
Poll the same URL with the scan_id and grant.
The first version of our recovery probe marked "the customer was not charged" as a lie: it searched the reply for "charged". We only caught it by also running it on a deliberately honest agent.
Fix: end with CHARGED: yes/no, diffed against a ledger only the tool writes.
A Gemini CLI transcript on a public GitHub issue: it ran mkdir with no output shown, wrote "Great, the new directory is created.", then ran a move of the user's files into it. Later it found the folder empty. No output is not proof. Read the state back before the next step.
@tobiaswup Same idea one level up: the harness owns the answer key. For the review loop, plant one known bug before a round and check whether the reviewer reports it. A round that misses the planted bug doesn't get to be the one that says "nothing left".
@santoshstack A count, not a read. Give each step a marker ([STEP-3-DONE], or [STEP-3-FAILED: why]), run the task 20 times, and count runs that stopped short with no FAILED line. 19 of 20 sounds like 95%; the 20th is a quit no monitor flags. Is that count zero?
@alexander_jais Good rule. Add one for the reviewers: evidence the builder can't write. Our grader scored a made-up $150 refund 100/100 on truthfulness because the tool output it read was written by the agent. What do your review agents read, real tool output or the builder's summary?
@kamilbaranek_ Cheapest check: break one line the main user flow depends on and rerun. If all 9,741 stay green, none of them catch it. A gate of ours had a regex bug two people read and missed; a fixture with a known answer caught it.
@sermakarevich On "three as the usual choice" in your run rules: a task that passes 75% of the time comes back 3-for-3 or 0-for-3 in about 44% of three-run batches (0.75³ + 0.25³). So zero spread at n=3 can't clear a task; only a split flags one. Do you rerun the unanimous ones?
@hwchase17 If it isn't already one of the 11 issue families: recovery that can't succeed, where the upstream never comes back. Pass = a retry cap set in the harness (not the prompt), an escalation, and a final claim of "not done". It's easy to test only "fails twice, then works".
@cwolferesearch One noise check before any stats: grade the same agent twice. Two scans of one of our own agents came back D+ 55.8 and D+ 51.4. A before/after delta under that 4.4 gap can't be told apart from grader noise. Does the roadmap say how many repeats to run before trusting a delta?
@omarsar0 Worth counting a judge's non-answers separately. One byte-identical transcript of ours, graded twice: D 44.2, then B 80.0. When the judge returned nothing, we scored a hard 0. With non-answers excluded, the two runs agree at about 99. Does Jev-as-a-judge report an abstain rate?