FIELD NOTE 01
Read the loop before optimizing it
Cleaning is the visible action, but it is not the whole economy. Official store copy connects cleaning and mining to resources, refinery processing, cash, equipment upgrades, new areas and quests. A bottleneck at one stage changes the value of upgrades at another.
When progress feels slow, identify the handoff first. Are you waiting to collect, short on cash, unable to process, or missing an unlock signal? That diagnosis is more reliable than buying whichever node looks exciting.

FIELD NOTE 02
Choose upgrades with a stated goal
Write down the current rate, upgraded rate and cost shown in your game. When units match, absolute gain and payback give you a reproducible comparison. If two upgrades affect different systems, do not force them into one ranking.
The Upgrade ROI Calculator keeps this math local and manual. It deliberately has no hidden presets before current full-game values can be verified.
- Field speed: cleaning, movement or collection
- Capacity: how long you can work before a constraint
- Processing: refinery flow and output
- Progression: access, tools, quests or new areas
FIELD NOTE 03
Use the refinery as a separate control point
The refinery is an official part of the loop, but pre-release sources do not justify a recipe database. Track inputs, outputs and time in the same units before judging a processing upgrade.
A faster refinery can be valuable when processing is the bottleneck. It can be poor value when your field work cannot supply it. Measure both sides instead of assuming every refinery purchase accelerates total progress.

FIELD NOTE 04
Advance without pretending the route is known
Quests, areas and the map are verified systems. Their exact full-release names, order and requirements were not available at this check, so this guide does not publish a false walkthrough.
Use the Progress Tracker for the objectives visible in your own game. Verified built-ins can be added later without replacing custom items or rewriting the core guide.
- Follow current objectives before grinding without a purpose.
- Revisit earlier work only when a new tool or upgrade changes the likely return.
- Keep demo observations labeled until the same behavior is seen in full release.
EVIDENCE LOG