How it works
The workflow is deliberately narrow: collect independent observations, align them to the diff, collapse overlap, and make uncertainty visible.
For how juror turns many model reviews into one useful review., 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.