Development & Sources report
Source Policy Separates Announcements, Store Data, and Preview Evidence
The site now labels what each official source can prove instead of merging all pre-release information into one confidence level.
Published · Official-source briefing
The verification model distinguishes Remedy announcements, first-party storefront capabilities, developer-authored system explanations, and observations from controlled official media previews.
What was confirmed
A dated announcement can prove a schedule, a store can prove a listed entitlement, and a played preview can describe its build; none automatically proves every release-version detail. This report isolates that specific official update so it can be linked from the matching navigation topic without turning a dated announcement into an unsupported all-purpose claim.
Community theories, retailer placeholders, converted prices, trailer frame counts, and unsourced databases remain insufficient for factual claims. The distinction is important before release: confirmed mechanics, storefront capabilities, preview observations, and details still awaiting retail verification are recorded separately.
The connected evergreen guide and FAQ cluster use this source as evidence, while final values, menu behavior, performance, quest counts, and balance-dependent recommendations remain subject to the shipped build. If Remedy or a first-party store changes the underlying information, the dated report remains the historical record and the current guide is revised.
Key takeaways
- Source types are labeled
- Claims stay within evidence
- Unknowns remain explicit
Official source
Remedy — current official game page
This report records the state of official information on its publication date. For changing specifications or launch details, follow the linked topic hub and current first-party listing.