Skip to main content
Annotations turn recorded traces into reviewed examples. Open Traces to label an outcome and record Ground truth: the expected result or behavior.

​
What counts as annotated?

A trace is annotated when it has ground truth or a Success label. Saving Failure requires ground truth explaining the correction. For example:
The purchase was through a reseller. The agent should have directed the customer to the reseller’s refund process instead of promising a direct refund.

​
Choose what to review

Failure resemblance highlights behavior similar to known failures. Novelty highlights behavior less covered by reviewed examples. Request Deep Analysis for an explanation and evidence to inspect. These signals help prioritize review; they do not set the trace’s label. Use random sampling as well when assessing overall quality.

​
Follow up

Open an issue for work that needs investigation, or propose a lesson when the finding contains reusable knowledge. Saving an annotation does not create either automatically. Start with the annotation workflow.