How it works
Counted comments are not value. Use explicit human outcomes, escaped defects, time to review, and uncertainty coverage to understand a workflow.
For code review metrics that do not reward noise, use the published configuration and source repository as the product record. Keep the workflow small enough to inspect, and record any exception in the pull request rather than assuming a model result is final.
Limits to keep in view
Models, providers, and benchmark conditions change. Juror does not replace code ownership, test suites, static analysis, or a human decision to merge. Treat unknown cost and unevaluated compatibility as explicit unknowns.