How it works
Each feature is designed around a concrete decision: what evidence to collect, what to merge, what to publish, and what to leave to the reviewer.
For juror features for clearer pull-request decisions, 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.