How we build the archive
Import, normalize, validate
Licensed datasets and permitted sources enter through provider adapters. Team aliases are normalized. Dates, scores and team participation are validated before storage. Competition, date and the two teams form a deterministic match identity; external fixture identifiers provide another identity where available.
Conflicts and confidence
Conflicting final scores go to the administration review queue and never silently replace a stored result. HIGH means a sourced record; VERIFIED requires an identified primary source or explicit editorial verification. Agreement between datasets that share an upstream source is not independent confirmation. Unknown events, lineups, player statistics and venues remain unknown.
Records and penalties
Records use published imported matches. A penalty shootout is recorded separately from the match score. The outcome of a shootout determines advancement and the displayed win classification when its separate scores are known. Ambiguous historical penalty-only rows are excluded pending review. Missing matches can change the calculated winning streak.
Corrections
Use the contact form with a match link, the proposed correction and a supporting source. Administrators can resolve conflicts, lock verified records and inspect the audit trail. No language model is required to publish a result.