Resource Chain Systems
How energy, water, oxygen, food, materials, AI compute, and habitability form one constrained survival chain. The briefing connects gameplay-facing systems to Mission Control language so future UI and game text can stay consistent.
System Role
This system should always explain what the player can do, what limit they are pushing against, what can fail, and how the result enters sector or planetary records. It should not read as an isolated stat.
Player-Facing Questions
- What resource or risk does the system expose?
- Which building, event, or technology changes it?
- What tradeoff appears when the value improves?
- Which global indicator or chronicle record should reference it later?
Player-Visible Chain
The Demo chain should read as energy enables extraction, extraction enables treated water, treated water enables oxygen and soil work, and those systems together protect the Embryo Vault. If one link is missing, the UI should show the blocked downstream promise rather than only a red number.
Planetary reporting should aggregate these local chains as pressure, not triumph. A sector can improve water-cycle integrity while increasing pollution pressure or maintenance exposure, and that mixed result should be visible in the next Mission Control snapshot.
Writing Rule
Keep the text concrete: threshold, deficit, redundancy, maintenance, delay, and consequence. Avoid fantasy phrasing, pure upgrade language, or claims that one action solves a planet-scale problem.
