Is every quality shift after a change a regression?

No. A regression is a drop the team didn’t want, and the exact same movement in a metric can be what a change was meant to do. Swap in a cheaper model on purpose and pass rate on a hard grader might fall a little; that’s an accepted tradeoff, not a regression, if the team chose it knowing the cost. Tighten a refusal policy and a false-refusal rate climbs; that’s the point of the change, not a side effect of it. Statistics alone can’t settle this, because a shift and a regression look identical in the numbers: both are the distribution moving after something shipped. What decides it is knowing what the agent was meant to do after the change, and checking the shift against that intent rather than against the old baseline by itself. The number alone can’t make that call; someone who knows what the change was supposed to do has to.

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