What happens when a Tessary classifier flags a trace?

Crossing the threshold writes a finding: a record that one trace tripped one classifier, and the score that did it. Nothing pages anyone yet.

LLM judgment only enters at this point, reading the finding instead of the raw trace, which is also where the model cost in the pipeline actually sits: the bill tracks how often the cheap checks fire, not how much traffic you serve. Triage then separates a real deviation from legitimate change, the harder half of the job. A tool your team changed on purpose looks identical to drift until something checks it against what actually happened.

What survives triage becomes a case, and a case is what gets attributed and, if it clears the alerting rules, what reaches a human. A flag that doesn’t survive triage never does.

keep reading

More on this.

Can I add a custom classifier for my own agent?Yes. Custom classifiers run alongside the built-ins on the same finding-and-threshold mechanism, fine-tuned to your own agent's failure modes instead of a generic one.answer →How much does it cost to run a classifier on every trace?Classifiers are included in Tessary's price of $0.001 per trace with a $100 monthly minimum. At 1 million traces a month that is $1,000, and every trace is checked.answer →What is a Tessary classifier?A narrow, cheap check that scores one production trace for a single property, cheap enough to run on all of it instead of a sample.answer →Everything on tessary classifiersThe definition, and every question answered under tessary classifiers.concept →

Send us the traces you already emit.

book a demo