Scope before certainty

The guide currently separates Steam 1.0 (Release) and Unstable Beta. A fact recorded for one branch is never silently reused for the other. The release seed is intentionally small: it records only what the saved official announcement supports and does not infer objectives, effects, rewards, enemy types, maps, or loadouts.

Trust states

Verified

Public source, applicable version, and a verification date are recorded. It may appear as a factual statement, but still links back to its source record.

Needs verification

The source is incomplete, conflicting, or does not support the needed level of detail. It may be logged as a limitation, but not converted into planner advice.

Community tip

A player strategy or subjective recommendation. It must identify its context and never be presented as an official mechanic. The current seed does not use community tips for recommendations.

How a record is reviewed

  1. Capture a public primary source or a clearly labelled supporting source.
  2. Record its URL, source type, access date, version scope, status, and short use note.
  3. Extract only facts the source supports; unknown fields remain Unknown / Not yet verified.
  4. Validate the version-isolated data release and write a change entry when records change.
  5. Review source links again before expanding a claim or a planner rule.

Current release boundaries

Steam 1.0 (Release)

Minimal verified seed. It records only facts supported by the saved official announcement snapshot; missing mission objectives and effects remain unknown.

Release date
2026-08-07
Sources
1
Mission types
1
Planner rules
1

Unstable Beta

Minimal verified seed. The saved official announcement confirms the Unstable Beta branch, but does not provide branch-scoped mission facts; no Steam 1.0 records are reused here.

Release date
2026-08-07
Sources
1
Mission types
0
Planner rules
0

What the planner does not do

The planner organizes verified mission facts and transparent preparation checks. It does not predict success, read a save file, send information to a server, or fill missing information with a generated loadout, level requirement, reward, or tactical claim.

Corrections and source issues

If a source is unavailable, stale, or appears to be attributed to the wrong version, the record should be marked for review rather than hidden. This launch does not publish a contact address, so it does not promise a response time. Use the source details and change log to assess the present coverage.