Evidence hierarchy
| Type | What we use it for | What it cannot prove alone |
|---|---|---|
| Official | Platforms, release date, player rules, accessibility, version notes and visible achievement text | A step-by-step puzzle route the source never documents |
| Captured route | Visible locations, interactions, route order and screenshots from a completed session | Unrelated claims in the upload description or universal target counts |
| Reporting | First-hand previews, interviews and clearly attributed observations | A current fact superseded by a live official page |
| Community | Recurring questions, field-tested coordination ideas and independent corroboration | A game rule, hidden requirement or platform announcement without confirmation |
How a guide is published
- Start with one specific question a player needs answered.
- Collect official facts, a captured route and relevant community questions where available.
- Check each sentence against the field its source can support.
- Use only screenshots that visibly match the adjacent instruction and add a source credit.
- Record the fact-check date and game version when the official source names one.
- Test links, image loading and page accessibility before publication.
Community posts and comments
Community discussion is valuable because it shows where real groups get stuck. It is also noisy. We label player advice as a community field note, seek an independent capture or official rule, and reject comments that conflict with first-party information. Votes and repetition can guide research priority; they do not turn a claim into fact.
AI-assisted work
AI-generated text is not treated as a source. Every factual claim must still point to an official page, a visible captured interaction, attributable reporting or a clearly labelled community report. Pages are not expanded with plausible but unsupported game details.
Spoilers and uncertainty
Necessary route spoilers appear in the guide that a player intentionally opens. Ending information is collapsed or omitted. If sources conflict on a hidden count, reward colour or trigger, the site does not publish a definitive number until the conflict is resolved. Claims that cannot be verified are omitted rather than presented as fact.
Corrections
Material errors are fixed in the page and recorded in the public corrections log with the date, old claim, replacement and source that resolved it. Cosmetic edits and spelling fixes are not logged individually.