MAZHATTERIX // EDITORIAL STANDARDS & CORRECTIONS
Last updated: August 28, 2026
MazHatterIX is built around personality, curiosity, testing, rabbit holes, and occasionally yelling at technology. The voice can be chaotic. The sourcing should not be.
How we label information
- Confirmed: supported by an official announcement, documentation, direct statement, first-hand testing, or other primary evidence.
- Reported: attributed to a named publication, journalist, creator, developer, company representative, or other identifiable source.
- Leak: information or material that appears to originate outside an authorized release. Authenticity, context, and final-game relevance may remain uncertain.
- Rumor: unconfirmed information that does not yet meet the standard for reporting as fact.
- Maz Take: opinion, interpretation, prediction, humor, or commentary.
Source priority
When practical, we prefer primary sources such as official announcements, patch notes, documentation, public records, direct statements, or first-hand testing. Reputable reporting, creator reporting, community posts, Reddit threads, social posts, and RSS items can provide useful context, but should be attributed according to what they actually establish.
RSS and Incoming Signals
RSS feeds and outside links are discovery tools. An Incoming Signal is not automatically a MazHatterIX article and is not republished as though we created it. Original publishers and creators should receive clear attribution and a path back to the original source.
Creator Shoutouts
Creator Shoutouts exist to send attention outward. When highlighting another creator’s post, channel, video, stream, or work, we aim to identify the creator, link the original, and make clear what is theirs versus our commentary.
Reviews
Reviews should disclose material relationships, distinguish testing from marketing claims, and use the MazHatterIX review framework consistently. Affiliate revenue, sponsorships, free access, or review units do not buy scores.
Corrections and updates
If a material factual error is discovered, we aim to correct it promptly. Developing stories may be updated when rumors are confirmed, leaks are debunked, release dates change, or new official information becomes available. Significant corrections should be made transparently when practical rather than silently rewriting history.
AI-assisted work
AI tools may assist the production process, but AI output is not treated as self-verifying evidence. See the AI & Content Disclosure for more detail.
Send a correction
To flag a factual error, broken source, attribution issue, or missing context, contact mazhatterix@gmail.com and include the URL of the relevant page.