Gameplay-tested records
A tested answer records what was visibly submitted and scored during a specific completed game session. The observation is stored privately first and does not become public merely because the game accepted it.
Three publication gates
Every public gameplay record must be verified, approved through a separate rights review, and explicitly approved for publication. Private test data and records marked as test fixtures cannot pass the public query.
Data provenance
Each imported dataset carries an immutable content hash, source label, rights basis, review state, and operational audit trail. Automatic collection stays off until documented reuse permission exists.
What “verified” means
A verified label confirms the stored observation matches the reviewed evidence. It never means the site can guarantee acceptance in every game version.
How hints are written
Editorial hints are derived from approved records and remain separate from observed scores. They do not use a paid language model or present an estimate as gameplay evidence.
Answer Checker limits
The checker performs normalized, case-insensitive matching against published records. No match means only that the answer is absent from the current dataset.
Corrections
Corrections should identify the date, question, disputed record, and supporting evidence. Approved updates remain traceable through the administrative audit history.