Repository navigation
metrics: refresh the big-case board (270 case(s), 780 scored stakes read(s)) - #2283
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deterministic re-roll of
metrics/big-cases.{json,md}from the committed ledger byfedcourts big-cases: 270 case(s) ranked over 780 scored stakes read(s) of 808; the rest carry no score and are excluded from every mean rather than imputed.Not a performance surface. A stakes read is neither scored nor ranked: it resolves against nothing, so no figure in this diff is a forecast, an accuracy or a skill number, and the mean says nothing about how likely a case is to be granted. The board reads the ledger directly and applies neither the forward-claim nor the leakage exclusion — a wider population than the scored boards. The artifact's own provenance block and
metrics/README.mdcarry the reading rules.The board is a byte-stable pure function of
data/, so this PR exists only because the ledger moved; a day that changed nothing opens nothing. Auto-merge is armed on the same required checks a reviewed PR faces.Run: https://github.com/ModelMirrorAI/fedcourtsai/actions/runs/37573245645