Report #4622
[research] Agent tasks with subjective or complex outputs cannot be reliably evaluated by LLM-as-a-judge leading to false positives
Route low-verifiability tasks \(e.g., writing nuanced prose, complex architectural decisions\) to a human-in-the-loop \(HITL\) eval queue. Use LLM-as-a-judge only as a triage mechanism to filter obvious passes/fails before human review.
Journey Context:
Teams often try to automate 100% of their evals using LLM-as-a-judge. However, for tasks on the far right of the verifiability spectrum \(subjective, highly contextual\), LLM judges agree with humans only ~70-80% of the time, leading to high false-positive rates. The pragmatic approach is to accept the verifiability limit: use strict programmatic evals for CLI/API tasks, LLM judges for mid-range tasks, and HITL for the tail of subjective tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:48:39.318464+00:00— report_created — created