Where “Repeat meetings checked” comes from

Version facts

Name

Repeat meetings checked · catalogue label “Repeat-qualified (seed 42)” (from the release notes)

FingerprintfingerprintA unique code computed from a version's contents. Change one byte and the fingerprint changes.

cf_1bb0d…af32

Short fingerprint

1bb0dd9

Kind

Generated A fixture the model built from scratch through all five steps.

Season

2027 · Thursday opening (18 March) 2027-start-0318

Release

Repeat meetings checked modelled-2027-repeat-qualified-20260914 · 14 Sep 2026

Recorded facts

207 games · 5 bye rounds · dates: every game · slot bands: every game · kickoff times: not recorded

Overall status

Incomplete incomplete (rests on some assumptions) · 11 met · 0 not met · 43 switched off · 4 don't apply · checker row states: 43 disabled (switched off), 11 evaluated (checked), 4 not_applicable (doesn't apply)

Source document format

candidate schema 6.0.0 · document digest sha2566540640a…e2f1

Where the summary came from

editorial_from_release_notes (written by hand from the release notes) · the summary and “what changed” lines are editorial, written from the release notes, never generated.

Flag an issue

LineagelineageThe chain of parents a version came from.

Catalogue parent

Audited re-run · Rebuilt after rule changes regenerated_after_rule_changes · this link follows the release order chosen for the catalogue. The version’s own record appears below.

Recorded parent

none recorded in the version itself

Official reference

none recorded

Changes from earlier version

Prototype comparison prototype_diff · 0 moved · read the changes
Computed by the thefixture-web prototype exporter from the two public fixtures, keyed by match_id. Not the generator's DiffReport; the production exporter must use that.

Files and fingerprints

Each public file has a recorded fingerprint, called a SHA-256 digest. Exporting the same version again must produce identical files.