Skip to main content
Each QA result answers one QA agent’s question about one trace or one task version. Read results in a trace’s QA view, in the Quality assurance section of a task’s Overview, and through the QA marks on traces, tasks, and the task grid.

​
Verdicts

A result that has not finished shows Pending. A result shows Error when the analysis did not complete and Cancelled when it was stopped; neither is a verdict, so run the check again.

​
Result marks

A trace’s mark combines its checks, and a task’s mark in the task grid combines its task checks with the trace checks on its traces. Open a mark to list each check’s result, problems first, and Copy them all as JSON.

​
Read a result

A result shows its verdict, its confidence, and a summary. Details lists its findings. Each finding has a short summary and a description that can include the root cause, why it matters, a suggested fix, the finding’s own confidence, references to the steps or files it is based on, and, for Failure Analysis, whether the agent, the environment, the grader, or the task is at fault. The copy icon on a result copies it as JSON. Each QA agent shows its latest result first, under Latest. Earlier results stay below it under Past runs, grouped by the run that started them; QA agents started together form one run. A task check’s result belongs to the task version it reviewed. A new version starts with no task-check results, and results of earlier versions are labeled Earlier version. Rate a result with the thumbs up or down below it, and add a note if you like. The rating goes to HUD and helps improve the QA agents.

​
Fix what QA finds

A failed check points at what to change: Then close the loop:
  1. Fix the task. Change the prompt, parameters, or rubric on the task page, which saves a new task version. Fix grading code or tools in the environment and deploy a new build. For Harbor tasks, fix the task directory and import it again.
  2. Keep bad rewards out. Invalidate traces whose reward measured a defect instead of the model.
  3. Run and review again. Run the task, then run QA on the new traces, or let automatic QA review them.
To hand findings to a teammate or a coding agent, open the task’s Traces tab and select Copy all. It copies the verdict, confidence, and summary of every completed check on the listed traces as Markdown.

​
Verdicts from HUD reviewers

HUD staff can review a QA result and record their own verdict, with an optional note. That verdict replaces the QA agent’s and keeps its findings, and the next run of the check supersedes it.

​
What public viewers see

When a trace is public, or its job’s runs are published with a taskset, anyone who can view it also sees your team’s latest result of each trace check: the verdict, summary, confidence, and findings. Evidence references, notes, errors, and the QA agent’s own trace stay private, as do task-check results and results recorded by other teams.