THE PROJECT / OUR PRINCIPLES
Editorial Policy
How Steam Game Wiki verifies game facts, reviews official announcements, handles unknown information, and publishes corrections.
Sources before certainty
We prefer official store pages, developer announcements, documentation, and directly reproducible evidence. Every published game reference includes its sources and review date. Detailed facts link to a source record, verification status, and applicable version when one has actually been established.
Source links make our work auditable. They do not guarantee that a developer description is complete, or that every claim has been tested in-game.
What we publish
A game must have a verified Steam AppID, matching official store URL, and substantive source-backed information. Wiki categories require published content. Gameplay guides require verified requirements and steps. Tool descriptions must match what the tool really does.
Unknown values remain unknown. We never substitute zero for missing data, invent release timestamps, manufacture card or recipe names, or claim a game version without evidence. Steam community tags are labeled separately from official store genres. They do not establish a game mechanic, search demand or player popularity.
Official news is reviewed first
Automated checks may find official announcements and propose review tasks. They do not publish articles, overwrite wiki facts, or silently approve a new game. A reviewer checks the original source, date, game, category, summary, and any affected facts before publication.
News is not automatically a patch. We only use “patch notes,” “hotfix,” or “major update” when the announcement supports that classification. We write concise original summaries and link to the original, rather than republishing announcements in full.
Dates and versions
The original three launch games have October 26, 2026 storefront dates. A user-supplied SteamDB observation refers to October 27 UTC, but that observation has not been independently rechecked. Additional games retain their own verified Steam calendar dates and relevant publisher or regional context. Exact UTC release instants remain unconfirmed. A calendar date alone is never converted into a fabricated release timestamp.
Content update dates describe substantive changes to a page and its evidence. Review dates describe when evidence was checked. They are not game release dates, patch dates, or proof of the current installed version.
Corrections and revisions
Content changes belong in a reviewed Git pull request. Editors preserve field-level source evidence, update the relevant facts and content hashes, inspect affected pages and tools, and run content and static-build checks before publication. Content hashes detect stale revisions; recalculating a hash does not assert that a fact has been reviewed. Git retains the revision history.
Automated validation checks structure and traceability. Human review is still required to judge whether the source actually supports a claim.
Discovery and keyword research
New game candidates and keyword suggestions are research records outside the published website. They do not automatically become public pages. Missing search volume and trend data remain null. SteamDB is only a manual reference unless explicit access is authorized; this project does not scrape it.