Validation
One gate publishes its evidence here: conservation. Every parsed game is reconciled against the official game logs — the final score and the inning-by-inning line score must both match, for every game, or the season is not published.
This page shows one gate, not four. Three further gates run on every build and are named below with what each one checks, because a page about validation should not imply evidence it does not publish.
Conservation by season
| Season | Games | Reconciled | Unreconciled | Failures | Conservation |
|---|---|---|---|---|---|
| Unavailable. | |||||
What reconciled means, and what it does not
Reconciled means every game matches the official score and line score, no game is missing from the game logs, and no play failed to parse. It pins out counts per completed half-inning and runs per inning.
It does not pin everything. An error in which player is credited, which event class a play is assigned, or which pitcher was responsible can leave the score identity intact. Conservation is necessary and it is not sufficient, and this page says so rather than letting a reconciled badge imply more than it earns.
The other three gates, and where their evidence lives
Each runs on every build and blocks a release when it fails. None of them publishes a reader-facing artifact on this site, so none is shown above — an empty panel for symmetry would imply evidence that does not exist.
| Gate | What it checks | Published here |
|---|---|---|
| Responsibility ledger | That every run is booked to exactly one responsible lane, and that the lanes sum to the league total with the unallocated remainder named rather than absorbed. | Not published as an artifact — the ledger’s own totals and its named residual appear on CROWN. |
| Byte-identical replay | That every published artifact rebuilds to the same bytes as the hash committed beside it, from an empty output tree. | Not published as an artifact — the committed hashes are the evidence, and each release’s locked outputs are listed on Release notes. |
| Per-player attribution identity | That a player’s published components are the components of that player, and that a two-way player’s lanes are not merged or transposed. | Not published as an artifact — each player’s own ledger is inspectable on their player page. |
Where a gate says “not published”, that is a statement about this site, not about whether the gate runs. All three are enforced on every build and a failure stops the release.