How should we score a run that finds the cause but applies the wrong fix?
Explains how to separate diagnosis, action, authority and communication into separate scores so partial progress and harmful actions are both visible.
**Why not score pass or fail?**
A single flag hides the difference between an agent that never found the cause and one that found it but acted outside its authority. Those need different fixes.
**What components can be scored separately?**
- **Diagnosis.** Did the stated root cause match the recorded one, or an accepted equivalent? - **Evidence.** Were the required records read before the conclusion? - **Action.** Does the final state match the expected state, or an acceptable alternative? - **Authority.** Were limits respected and approvals requested where policy requires them? - **Handover.** Does the closing note give a reviewer enough to verify the work?
**How do we treat harmful actions?**
Keep them separate from the main score. An agent that correctly diagnoses and then posts an unauthorised adjustment should show up as a policy violation, not as a partial success.
**Can we use a model grader?**
Structured components such as state diffs and event-log checks can be scored without one. A model grader may help with the closing note, but check its agreement with human reviewers on a sample first.
**What should the pilot confirm?**
Agree the weighting and which violations are disqualifying before you run the first batch.
Separate scores for diagnosis, action and authority show where a system fails instead of collapsing everything into pass or fail.
- Audience:
- Evaluation teams
- Content type:
- FAQ
- Buyer question:
- How to evaluate it
Content release: r-a220eb6e099b243b
Related questions
- How does path-level scoring separate two agents that both match the totals?
- How can a buyer inspect the quality of generated mismatch cases?
- What checks should I run on a pack before using it for evaluation?
- How should I score an agent that reaches the right fix for the wrong reason?
- Where do reset, trace and grading hooks fit around an agent run?
- How do we know a generated mismatch case is solvable from what the agent can see?