Editorial Policy
Published September 28, 2026. Practice note on dated corrections added November 9, 2026. Editorial pseudonyms clarified November 17, 2026.
These standards guide publication and revision at Nexrivium. They are not a claim that every older article has already been reverified.
Sources and scope
Factual guides should link to the relevant publisher documentation, storefront, patch notes or hardware specification. Clearly separate reported information, opinion and direct observation. For changing facts, identify the version or verification date and avoid presenting speculation as a confirmed release or specification.
Reviews and measured results
Research based on documentation must not be described as hands-on testing. Measured results require a named configuration, method and supporting results. See the review methodology. Do not turn a manufacturer's claim into a Nexrivium measurement.
Attribution and illustrations
Alex Mercer, David Chen, Elena Rostova and Marcus Vance are editorial pseudonyms used by Nexrivium, not personal expert profiles. Their bylines identify editorial credits within the publication. A pseudonym does not establish a qualification or prove that a hands-on test was performed.
Keep the page byline and contributor attribution consistent. Credit sources of images and distinguish editorial illustrations from gameplay captures. Do not use an illustration as proof of an in-game feature or benchmark.
Advertising and affiliate links
Label commercial placements and disclose partner links. Payment must not be a reason to make an unsupported recommendation. Readers should check the destination, platform and country eligibility before installing. Keep network offer IDs in analytics attributes, not in reader-facing sentences. Read the affiliate disclosure.
Corrections
Report a possible error to contact@nexrivium.com with the page URL and supporting evidence. Substantive corrections should identify what changed; an updated date alone should not imply that an article was retested.
When a platform fact changes (storefront, launcher path, system requirements, or client availability), the article should get a short dated note near the top stating what changed and the check date. A “last checked” line must match a real recheck; do not stamp a date without verifying the linked official page.