How it works
A useful review must preserve each reviewer observation while returning a human-readable decision. Juror uses anchors, similarity, and a referee stage to do that.
For one bug should produce one finding., 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.