Overview

This project is a narrative-driven automation and expansion game about an uploaded human mind forced back into matter at the moment matter itself is becoming unstable.

The player is not a captain, not a kingdom, and not a faceless builder. The player is a single continuity of consciousness stored in a Mind Disk, embodied through machines, growing from one lonely industrial outpost into a civilization-scale stabilizing force against the spread of Dark Flux.

The design must feel coherent at every scale. That coherence comes from one rule:

The player keeps solving the same industrial and strategic problems, but at larger physical scales and with higher stakes.

The early game is not a disposable tutorial. It is the seed form of the entire campaign. The player begins by mining ore, moving items, building machines, and surviving with limited embodiment. Later, those same concerns become regional shipping, orbital construction, shuttle scheduling, asteroid extraction, gate routing, and star-scale energy allocation.

Design pillars

1. Chronological causality

Mechanics should unlock when the story makes them inevitable.

• backup and saving appear when mind continuity becomes a solvable engineering problem
• remote operation appears when communications and control infrastructure become robust
• orbital industry appears when planetary industry stops being enough
• interplanetary routing appears when the player must reach resources and positions that cannot be supplied from one world
• gates and time manipulation appear only after precursor and Flux-related breakthroughs
• elemental descent appears only after raw Flux can be captured, contained, and translated into an inward stabilization program
• cloning remains late because the fiction should treat it as dangerous, not routine

2. Embodiment matters

The player is software, but gameplay happens through bodies, machines, towers, and infrastructure. Swapping bodies, risking death before sync, and gradually externalizing labor into automation should all feel central rather than ornamental.

3. Automation is identity, not convenience

The game should not spend too long pretending to be a manual survival game. The real fantasy is the growth of intelligent industry under existential pressure. Manual work exists to establish scale and vulnerability, but automation must become exciting early.

4. Scale should expand, not fracture

The game is intentionally broad, but it should never feel like disconnected minigames. Planetary logistics, station management, frontier expansion, and elemental stabilization should all share the same mental model:

• production nodes
• transport links
• buffers
• power
• risk
• response

5. Narrative stakes should produce mechanics

Dark Flux is not just lore wallpaper. It justifies:

• the urgency of industrial expansion
• the need for precursor recovery
• the eventual rise of stabilizers
• the danger of reckless acceleration
• the possibility of rogue minds, unstable gates, and dangerous scaling choices

High-level game shape

The campaign grows through four major working scopes:

1. Planetary industry
2. Orbital and station industry
3. Interplanetary and later interstellar expansion
4. Elemental stabilization inside matter

Each scope has two operating layers. That eight-layer structure becomes the primary backbone of the design and of the user experience.

Why the scope model matters

The scope model solves a structural problem common in large simulation games: expansion often introduces new maps and screens that behave like separate products. Here, each larger scope should feel like a strategic extension of the previous one.

At the planetary level, the player learns local production and then macro distribution.

At the station level, the player learns external infrastructure and internal industrial orchestration.

At the frontier level, the player learns route creation and then exploitation of distant opportunities.

At the elemental level, the player learns local lattice repair and then field-scale propagation of stabilization through matter itself.

That is the intended rhythm of the whole game:

• build competence locally
• push outward
• create a new layer of logistics
• then industrialize that new layer
• finally turn inward and apply the same logic at the scale of matter

The rest of this book elaborates that structure in detail.