Editorial Policy
How UltraMythos selects sources, verifies factual claims, distinguishes analysis from testing, and handles corrections.
1. Primary-Source Hierarchy
Whenever UltraMythos states a technical specification, API price, context limit, or release date, we require a verifiable primary source: official developer documentation, published system cards, peer-reviewed technical papers, or manufacturer specification sheets. We do not treat social media rumors or unverified aggregator blogs as factual evidence.
2. Epistemic Labeling: Announcements vs. Testing vs. Spec Analysis
Every article and comparison on UltraMythos carries an explicit epistemic badge:
• Company Announcement / Official Spec: Summarizes what a vendor has officially released or documented, clearly attributed to the company.
• Specification & Architecture Analysis: Evaluates products using engineering principles (such as optical sensor geometry or memory bus bandwidth math) and official documentation. We never claim to have physically bench-tested a hardware device in person when our analysis is based on specifications and published technical documentation.
• Workflow & Documentation Audit: Inspects software pricing tiers, terms, privacy controls, and CLI/UI workflows directly against current public documentation.
3. AI-Assisted Editorial Standards
We prohibit unedited 'AI slop,' keyword-stuffed filler paragraphs, fabricated quotes, and invented benchmark charts. Any computational assistance used for structuring data tables or checking code syntax is verified line-by-line against primary sources before publication.
4. Corrections & Update Timestamps
We display an 'Updated' date on an article only when a substantive factual revision, pricing update, or correction has occurred. To report an error, email contact@ultramythos.com or abuse@ultramythos.com.