Versions

Every published score names the rules that produced it. This is the archive those names point at.

A weekly snapshot pins four things — the contract a prediction was written against, the case registry it answered, the reference pool it was scored on, and the scoring metric that turned the answer into a number. Each pin on a leaderboard row is a link, and each link lands here.

Not current documentation — those rules, as of that week. If the bands move in November, a score published in September still points at the September bands, because the September score was never computed against anything else.

Two rules that make this worth reading

A version page is written once and never edited. If something on one of these pages is wrong, the correction is a new version and a changelog entry naming what it replaced. Editing a version page in place would make the archive worthless: a reader could no longer tell whether the page describes the rules that ran or the rules someone later wished had run.

A version is retired, never deleted. A pin from a snapshot published two seasons ago has to still resolve. Nothing here is removed once it has scored a week.

What is frozen, and what is not

The facts on each version page are generated from the artifact that version is — how many cases the registry holds, which seasons a pool was cut from, how many band grids it carries. They are not prose someone maintains alongside the artifact, because that copy would drift and a version page that misdescribes its own version defeats the purpose.

One thing on each page is live: which published runs used it. That changes every week, so it is fetched when you open the page and says so plainly when it cannot be loaded, rather than showing a figure that was true at deploy time.

The archive

Contract

Case registry

Reference pool

Scoring metric

Entity crosswalk

Reading a pin

The four pins under a leaderboard row answer four different questions.

PinAnswers
ContractWhat was the participant asked, and in what vocabulary?
Case registryWhich transfers were in the cohort, and under which eligibility rules?
Reference poolWhat were the bands, and what seasons were they cut from?
Scoring metricHow was the answer turned into a number?

A fifth, the entity crosswalk, is not pinned on the board but is listed here: it is how a transfer resolves to the player whose appearances are measured, and a reader auditing a score eventually reaches it.