Methodology | Quasimorph Mission Guide

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. Official patch facts and community-maintained gameplay references are stored separately and carry their trust label into every tool that displays them.

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

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

Current release boundaries

Steam 1.0 (Release)

Steam 1.0 / Patch 1.0.2 evidence release. Official release facts, source-labeled community signals, and prohibited claims stay separate; mission walkthrough details remain unknown until version-scoped evidence is captured.

Release date: 2026-08-20
Sources: 30
Mission types: 14
Planner rules: 1

Unstable Beta

Steam 1.0 research does not populate the Unstable Beta dataset. This branch retains only its compatibility evidence and never receives a silent fallback from the default branch.

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

What the planner does not do

The planner builds a copyable preparation brief only from verified mission facts. A community-maintained type can still be selected for identification, but its output is labelled Community field notes, the checks are presented as items to confirm in-game, and the copy-as-verified action remains unavailable. The planner 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.