How do you measure whether a grader itself is accurate?

You run it against a set of cases with a known right answer, human-labeled, and compare the grader’s verdict to that label on each one. The result is the same pair of numbers used to evaluate any classifier: precision, how often a case the grader flagged was actually bad, and recall, how much of what was actually bad the grader caught. A grader with low precision wastes a team’s time chasing false alarms; one with low recall gives false confidence by staying quiet on real failures.

This is why a labeled golden set earns its keep twice: it tests the agent, and it’s the ground truth a grader’s own accuracy gets measured against. A grader with no labeled set behind it is an unverified claim about what it catches. Recalibrate the same way you’d recheck any measurement: re-run the grader against the labeled set whenever the agent’s behavior, or the grader’s own prompt, changes underneath it.

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y