Editorial policy

Sources

Official developer pages, support documents and platform listings are the starting point for announcements and product details. A factual claim should have a source that supports that specific claim. Community discussion can suggest a question to investigate; it does not automatically establish the answer.

Labels and limits

• Officially named: a primary source identifies the person, place or item.
• Editorial analysis: our explanation or recommendation, distinguished from an announcement.
• Not verified: no adequate evidence has been recorded for this detail.
• Tested: reserved for a result supported by actual testing, with conditions recorded.

Originality and AI assistance

AI tools may assist with outlines, drafts and formatting. They must not be cited as proof, used to invent testing, or used to disguise copied reporting. We aim to add practical explanations and clearly organized references rather than rewrite another publication’s articles.

Corrections

Send the page URL, the disputed detail and a supporting source through the contact form. A correction should change the affected text and its verification date; a significant factual correction should also include a note explaining what changed.

Spoilers and speculative claims

Story-sensitive guides should identify spoilers before major revelations. Predictions and interpretations must be labelled. Leaked personal information and unverified accusations do not belong in this database.

Commercial relationships

This local build has no advertising code or affiliate purchase links. If monetization is added, relevant disclosures and privacy information must be updated before it is enabled.