Facts begin with sources
Current release dates, patch details, incidents, policy changes, statistics, and direct claims should be tied to source records. Official publisher material is preferred. Verified repositories and platform documentation can support technical coverage. Published articles display their recorded source links.
Research agents and human publication
Research agents can read approved sources and prepare structured drafts. They cannot publish stories or mark claims verified. An authorized human editor reviews the evidence and decides what is published.
Community reporting is labeled
Community reports provide firsthand experience and questions. They are attributed as community context and do not replace an official source for a factual platform claim.
Rankings show their method
A top list should state its criteria, evidence, data window, limitations, and any commercial relationship that could affect selection. Rankings without a recorded methodology remain unpublished.
Corrections stay visible
When a material claim changes or proves wrong, editors update the article, record the review time, and add a visible correction note. Readers can report questionable code records through the database where that feature is available.
AI and human writing
Automation may help gather evidence and structure drafts. Editors confirm that citations support the claims and revise drafts for the specific player question. Search optimization does not justify invented facts, hidden sourcing, fake community activity, or pages created only to manipulate rankings.