Sources — CONTROL Resonant Companion Citations | CONTROL Resonant
Quick answer: The CONTROL Resonant companion cites official Remedy material and Helpshift-style support docs first, then storefronts and platform blogs, then attributed reputable press, then corroborated community reports when official checklists are silent. Prefer official Remedy and storefront pages when facts change after launch. Corrections go to hereisisrar@gmail.com with a URL and the incorrect line so the live page can be fixed.
What does this dossier cite?
Primary outbound hubs on the Sources index include Remedy’s game hub and release-date articles, controlgame.com, Nasdaq / Remedy editions and launch PR, Steam, Xbox, PlayStation Blog, Epic Games Store day-one PC notes, and GeForce NOW day-one cloud notes via Remedy. Platform blogs such as PlayStation Blog and Xbox Wire sit in the same official-adjacent tier for platform-specific claims.
Press and aggregate citations called out on the thin Sources page include Metacritic, OpenCritic, GameSpot, IGN, PC Gamer, DualShockers, Polygon, and The Shortcut roundups, plus named outlets such as GamingBolt for wishlists and Wccftech for H1 2026 context where those links are used. Social pointers include ControlRemedy on X, Instagram, Discord, and r/controlgame for community corroboration—not as a replacement for primary docs.
Source hierarchy in practice
Editorial standards rank sources as: (1) official Remedy articles, Helpshift / support docs, and Nasdaq or company PR when editions or dates change; (2) platform storefronts for price, DRM, language, and storage claims; (3) named press outlets for scores and hands-on playtimes, always attributed; (4) multiple independent community reports for map-gated side content when no official checklist exists. If a claim cannot be traced, it does not ship.
| Tier | Examples on this companion |
|---|---|
| Official | Remedy hub, Helpshift / support, company PR, controlgame.com |
| Storefronts | Steam, Xbox, PlayStation, Epic, GeForce NOW notes |
| Press / aggregates | OpenCritic, Metacritic, named reviews |
| Community | Multi-report routes when official docs are silent |
Primary outbound hubs worth bookmarking
- controlgame.com — official marketing / news
- Steam — CONTROL Resonant — PC storefront, reviews, news
- OpenCritic · Metacritic — critic aggregates
- PowerPyx trophy roadmap — deep Platinum checklist
- Twitch category — Drops / Sierra Outfit notes where cited
- NVIDIA GeForce bundle — RTX 50 promo article
Those hubs are starting points, not an exhaustive legal bibliography. Individual guide pages should still attribute the specific Remedy post, storefront listing, or press outlet used for a contested date, edition claim, or score.
How corrections work
Email hereisisrar@gmail.com with the page URL, the incorrect line, and a better source if you have one. Material errors are corrected on the live page. The standards page states that known-wrong launch rumors are not left framed as fact. A correction updates the dossier and, where relevant, bumps a verified or last-reviewed stamp rather than silently swapping copy without accountability.
Community reports can prompt a review, but a single unverified tip does not automatically overwrite an official Remedy or storefront statement. When official docs later contradict an earlier community route, the official source wins and the guide is revised.
How Sources relates to About and Editorial standards
About explains that the site is an unofficial companion and what categories it publishes. Editorial standards explain how research is ranked and what the site refuses to publish. Sources is the outbound citation index and correction entry point for factual disputes. Use About for affiliation context, Editorial standards for process, and this page when you need the actual primary links the dossier prefers.
Prefer official Remedy and storefront pages whenever launch facts, edition SKUs, DRM notes, or promo windows change. Secondary roundups are useful for discovery, not for beating primary dates. That preference is why this index leads with Remedy, Helpshift-style support, and storefront hubs before press aggregates.
When press and community sources are appropriate
Named press outlets are the right tier for critic scores, hands-on playtimes, and attributed reporting—always with the outlet labeled. They are not the right tier for quietly overwriting a Remedy launch date or a storefront DRM claim. Community corroboration is appropriate for map-gated side content when official docs stay silent, and those lines should be marked community-sourced rather than dressed up as studio confirmation.
Social channels such as ControlRemedy on X, Instagram, Discord, and r/controlgame help surface questions and player reports, but they do not outrank Helpshift-style support docs or storefront listings when those sources conflict. Trophy deep-dives such as PowerPyx remain useful outbound hubs for Platinum checklists while still sitting below official edition and date announcements for buyer facts.
If you are correcting a page, include the better primary link when you have one—especially Remedy, Helpshift, or a storefront URL. That makes it faster to verify and ship the fix without leaving two competing claims live. The about page explains why the companion exists; editorial standards explain the hierarchy; this sources index is where the outbound citations and correction mailbox meet.
Affiliation and scope: about. Research and correction process: editorial standards.