Every change to the automated reviewer (its prompt, the policy, the model, the code around it) is a release. Before it ships, the new version decides the same 60 gold-labeled cases several times, and this page answers two questions: can we trust the measurement, and is the new version at least as good as the current one? Each candidate below is a real set of runs from the study. Any run can be opened in Can I trust this eval run? to see its checks and evidence.
The fingerprint is a short hash of everything that defines a build: model name, prompts, information sent to the model, dataset, code and environment. Same fingerprint, same build. All runs come from one day of the study, so the time ranges overlap; in a real pipeline each candidate would follow the last release.