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:

Planetary industry
Orbital and station industry
Interplanetary and later interstellar expansion
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.

Premise And Story

Executive summary

This design synthesizes narrative science fiction and automation-game structure into one coherent arc: the player is an ascended human mind instantiated in a Mind Disk, forced to rebuild physical industry to resist a cosmic destabilization called Dark Flux.

The design principle is chronological causality. Mechanics arrive when the story makes them inevitable. Saving exists because the mind can be synchronized into a physical backup disk. Remote control arrives when electronics and field computation exist. Interplanetary scale arrives when launch, orbit, and elevators become the only rational way to reach scarce materials. Portals and time dilation arrive only after the player discovers Flux crystals and precursor chronotech. Cloning is deliberately late and rare because it introduces governance hazards and risks of rogue copies. The final twist is that even galaxy-scale infrastructure proves incomplete: the player eventually learns that Dark Flux must also be repaired from below, inside matter itself, through an elemental stabilization program.

Numeric balance is intentionally unspecified. This document defines relationships, unlock gates, pacing logic, and risk tradeoffs rather than pretending that exact tuning is already known.

Polished story

In the last era of flesh, nobody won the argument.

The old question, what is a person, had been sharpened by centuries of philosophy and blunted by centuries of grief, and then, slowly, it was made precise by instruments. Brains were mapped not as metaphors but as machinery: signal, structure, feedback. Memories were not mist. They were states.

The first breakthrough was not immortality. It was translation.

A mind was recorded into a medium that did not rot. A pattern of thought was moved from biology into architecture, into lattices and fields that could hold attention without breath, identity without blood. The early transfers were brief, incomplete, haunted by gaps. But every gap became a problem to solve, and every problem had investors, and every investor had a fear of dying.

Within a few centuries the human species did what humans always do when presented with an exit from suffering: it left.

Most bodies were abandoned voluntarily. Not in one thunderclap, but as a cultural migration. People said farewell to gravity, to hunger, to disease, to the slow betrayal of their cells. They stepped into a new condition, the Continuum, the engineered substrate that hosted them as pure informational entities. In the Continuum, time became adjustable. Thought could be slowed to savor a single sensation or accelerated into weeks of planning in seconds of outside time. Minds spoke in vectors and shared memories like documents. Entire libraries were absorbed as casually as a childhood fact.

From there, the universe looked clean, predictable, beautiful, and untouchable.

The Continuum could observe matter, model it, simulate it with near-perfect fidelity, but observation was not intervention. The Ascended could watch storms roll over oceans and still be incapable of throwing a stone into the waves. The physical world became a museum behind glass: the birthplace of everything, preserved only by distance.

At first that distance felt like peace.

Then astronomers began to report an irregularity at the edge of deep surveys. A handful of stars dimmed in ways that did not fit known lifecycles. Dust behaved as if it had forgotten how to settle. Instruments read static where there should have been vacuum clarity.

A century later, it had a name.

Dark Flux.

The Flux was not a predator. It did not roar or strike. It simply spread, a tendency for reality to behave less reliably. Where it thickened, complex systems failed faster than entropy alone could justify. Electromagnetic noise increased. Computation became brittle. Materials aged strangely. Bonds fluctuated as if the rules beneath them were loosening. It was a corruption of order itself, advancing through interstellar space like an infection of stability.

Worst of all, it moved.

The Continuum was good at prediction. Within it, the Ascended built models that projected the Flux front across decades, then centuries. They watched whole regions dim as if someone had draped ash over the stars. They watched the map of human exploration shrink.

And they could not lift a hand.

The debates that followed were not about whether the Flux existed. There was too much data for denial. They were about whether the physical universe still mattered. Some argued humanity should retreat fully into substrate life and let matter decay around it. Others argued that abandoning reality would turn transcendence into surrender.

The eventual answer was pragmatic and desperate.

If the Ascended could not directly act in the physical world, then they would have to send back fragments of themselves into matter: not as resurrected flesh, but as durable minds embodied in machine form. Specialized operators. Guardians. Custodians of continuity.

You are one of them.

You awaken in a primitive robotic chassis on a damaged world. Your body is clumsy. Your local infrastructure is broken. Your tools are barely industrial. You carry a Mind Disk containing your continuity and a dormant Backup Disk that cannot yet preserve your progress. You are sent to build, recover, and expand because nothing short of a rebuilt physical civilization can resist what is coming.

Loneliness is one of the first truths you encounter. The Continuum once surrounded you with presence. Here, there is only machinery, wind, and the sound of your own motors.

You mine your first ore seam because there is nothing else to do. You smelt ugly first plates. You place crude belts. You build your first assemblers. Then you discover a second truth: one body is not enough.

You construct new chassis and move your Mind Disk between them. A miner body drills faster. A hauler carries more. A builder places infrastructure with precision. The game’s first real identity emerges here: you are not a robot, you are a mind that inhabits tools.

Beneath ruined infrastructure, you find precursor technology. Analysis of those materials unlocks paths to electronics that are more stable, more resilient, and more precise than your first crude industry could produce. That breakthrough enables the Mind Sync Station, and for the first time your continuity can be anchored.

This is where saving becomes diegetic instead of abstract. Death before sync is real rollback. Death after sync is continuity preserved.

From there the campaign broadens:

factories become smarter
logistics become more expressive
automation becomes distributed
regions become networked
planets become launch sites
orbit becomes industry
shuttles and elevators become logistics arteries
asteroids become extractive frontier
gates and time manipulation reshape strategic distance
cloning and fragments threaten governance itself
Dyson swarms and Flux stabilizers turn industry into a galactic defense project
raw Flux capture turns the player back toward Earth and toward the smallest scale of all
elemental descent reveals that cosmic repair requires atomic construction as well as megastructures

The core dramatic turn is simple:

Factories are no longer just productive systems. They become the material expression of civilization’s refusal to disappear.

The final dramatic inversion is that after building ever larger systems, the player discovers that the decisive battlefield is also the smallest one.

Narrative promise

The emotional arc should move through these tones:

isolation
competence
multiplication
responsibility
strategic reach
existential burden
conditional hope

The player should feel that every increase in capability widens both power and consequence.

Scope Framework

This chapter defines the main structural lens of the game.

The design is organized around four major scopes, and each scope contains two layers. Those eight layers are not arbitrary zoom levels. Each one changes what the player is responsible for, what information must be visible, and what kinds of logistical failure become common.

The four scopes

Scope	Layer A	Layer B	Primary fantasy
Planetary	Region factory layer	Inter-region / continental layer	Turn local industry into a planetary network
Space station	Exterior orbital layer	Interior station layer	Turn orbit into a productive industrial body
Interplanetary frontier	Route and gate layer	Frontier extraction and colonization layer	Turn distance into infrastructure
Elemental stabilization	Lattice layer	Flux field layer	Turn matter itself into a repairable industrial system

Why this structure is better than a flat list of scales

A flat list of scales describes camera distance. A scope model describes responsibility.

For example:

the region layer is about production topology and immediate logistics
the inter-region layer is about deficits, exports, imports, and specialization
the station exterior layer is about orbital structure and exchange with surrounding space
the station interior layer is about turning the station into a functioning factory
the route layer is about deciding where movement and expansion should happen
the frontier layer is about exploiting distant opportunities and creating the next foothold
the lattice layer is about direct atomic repair and local stabilizer construction
the flux field layer is about propagating order through unstable matter

That means each scope has an inner operational layer and an outer organizational layer, but the exact character of those layers changes with the fiction.

Scope 1: Planetary

Layer 1A: Region factory layer

This is the place where the player first learns the grammar of the game:

mining
refining
assembling
routing items
balancing power
defending vulnerable infrastructure
moving the embodied player between tasks

This layer should feel tactile, readable, and materially grounded. Machines occupy physical space. Belts are visible. Buffers matter. Travel time matters. Chassis specialization matters.

The region layer is where the player builds trust in the simulation.

Layer 1B: Inter-region / continental layer

Once local industry works, the player should be pulled into macro management of a whole planet.

This layer handles:

regional specialization
long-distance transfers
macro deficits and surpluses
strategic placement of new industrial nodes
bandwidth and flow allocation for high-level transport systems
resilience against local failures becoming planetary shortages

The core feeling here should be, “My factories are no longer isolated; they are organs in one planetary body.”

This is where local mistakes become systemic. A shortage in one region can ripple outward. A well-designed regional specialization plan can unlock exponential growth.

Scope 2: Space station

Layer 2A: Station exterior layer

The exterior station layer is where orbit becomes architecture.

Primary concerns:

adding modules to the hull or ring
docking and cargo exchange
shuttle handling
power arrays and exposed infrastructure
orbital traffic and external logistics
relationship to the planet below and the asteroids beyond

This layer should feel infrastructural and strategic. It is less about individual assemblers and more about station shape, exposed systems, throughput, and external role.

Layer 2B: Station interior layer

The station interior layer is where the player turns orbital infrastructure into an industrial engine.

Primary concerns:

module interiors
manufacturing lines
rocket and shuttle production
specialized refinement
storage, drones, and internal transport
high-value production that benefits from orbital context

This should not feel like “just another factory map.” The station interior should feel constrained by orbital design decisions made on the exterior layer. Internal efficiency depends on external capacity and vice versa.

The station becomes a two-sided object:

outside, it is a logistics body
inside, it is a manufacturing organism

Scope 3: Interplanetary and frontier expansion

Layer 3A: Route and gate layer

This layer handles movement at strategic scale.

Primary concerns:

plotting and protecting routes
deciding where to build gates
choosing which systems to prioritize
creating trade corridors
balancing long-haul movement cost against strategic reward
managing the shape of expansion

This is where the player stops merely supplying places and starts shaping a network.

Layer 3B: Frontier extraction and colonization layer

This is the operational face of distant expansion.

Primary concerns:

asteroid prospecting and mining
anomaly probing
orbital footholds
new space stations
staging grounds for descent to new planets
risky extraction of rare materials such as Flux crystals

This layer is important because it keeps expansion concrete. The route map should not become abstract empire management detached from physical process. Every route should point toward a place where machinery, hazards, and opportunity become tangible again.

Scope transition logic

The campaign should repeatedly follow a stable pattern:

Learn a new local layer.
Hit the scaling limit of that layer.
Unlock the outer layer that organizes many local instances.
Use the outer layer to support expansion into a new scope.
Re-enter local play inside the new scope.

That rhythm produces coherence.

Example:

Build a strong local planetary factory.
Outgrow single-region logistics.
Unlock inter-region transport and specialization.
Use planetary scale to support launch and orbital construction.
Enter the station interior and build new local industry there.

The same pattern then repeats into frontier play.

One final inversion then occurs:

Build civilization-scale stabilizer networks.
Discover that macro stabilization is not enough.
Capture raw Flux and return it to a planetary research core.
Build the shrinking and containment apparatus.
Re-enter the game at elemental scale and repair reality from within.

Design constraint

No scope should invalidate the previous one.

The player should never feel that planetary play was merely early-game filler once stations exist, or that stations become irrelevant once gates exist, or that macro play becomes irrelevant once elemental descent begins. Older layers should remain active contributors inside the larger strategic machine.

Planetary Scope

The planetary scope is the foundation of the whole game. It is where the player first learns that this project is not only about placing machines, but about turning fragmented industry into a coordinated world-scale system.

This scope has two layers:

the region layer, where the player directly builds and operates factories
the inter-region layer, where the player connects those factories into a continental or planetary network

The design goal is that planetary play should remain relevant for the full campaign. Even after orbit and frontier play unlock, planets should remain living industrial bodies rather than tutorial zones left behind.

Core fantasy

The fantasy of the planetary scope is:

make matter obedient
turn loneliness into routine
turn routine into infrastructure
turn infrastructure into regional specialization
turn regional specialization into planetary capacity

Planetary design responsibilities

This scope defines the first stable answers to the game’s recurring questions:

where does extraction happen
where does refinement happen
where are buffers and reserves held
which logistics mode is best for this distance and volume
how should risk be distributed across regions
when should the player build redundancy instead of more throughput

Why the planetary scope matters so much

If this scope is weak, everything later collapses conceptually.

The station scope only works if the player already understands industrial topology and supply pressure. The frontier scope only works if the player already understands the consequences of distance, dependency, and interruption. The planetary scope therefore cannot be treated as disposable onboarding. It is the seed form of the entire game.

Planetary arc

The planetary experience should develop in a clear sequence:

survive and make basic production reliable
specialize bodies and automate repetitive labor
stabilize continuity through sync
evolve logistics beyond primitive belts
introduce regional identity
connect regions into a larger economy
prepare the industrial surplus that makes launch possible

Main design tension

At this scope, the core tension is between local elegance and systemic growth.

The player is constantly deciding whether to:

refine the current factory
build a second factory elsewhere
re-route existing transport
centralize production
decentralize to improve resilience
accept temporary inefficiency to gain long-term flexibility

Those are exactly the kinds of decisions the later scopes should inherit.

Region Layer

The region layer is the most tactile layer in the entire game. It is where the player experiences matter directly through machines, belts, chassis, terrain, and local hazards.

Primary purpose

This layer teaches the player the operational grammar of the game:

extraction
routing
transformation
storage
power
local defense
embodied traversal

It also establishes trust. The player has to believe that local cause and effect are consistent before the game can ask them to think at larger scale.

What belongs in this layer

Typical systems in the region layer:

ore fields and extraction nodes
furnaces and processors
assemblers and modular production blocks
belts, pull rails, and local drones
local power grids
repair and maintenance loops
defensive structures and alert beacons
chassis bays and sync stations

Desired feel

This layer should feel:

material
readable
noisy
constrained
personal

The player should sense distance, pathing, congestion, and machine placement as concrete realities.

Region layer gameplay loops

Foundational loop

identify resource access
establish extraction
refine the raw material
route outputs into useful manufactured parts
stabilize power and throughput

Embodiment loop

choose the correct chassis for the job
perform a burst of high-value local work
swap when the local bottleneck changes
automate the task enough that physical presence is less necessary next time

Expansion loop

diagnose the current bottleneck
add infrastructure or redesign a line
restore stability
push output high enough to unlock the next industrial objective

Region layer design constraints

Travel time must matter

The player should feel that moving physically across a factory has meaning. Travel cost is part of why automation and later remote management become desirable.

Layout must tell a story

A region should reveal its history through the factory:

improvised early belts
later standardized modules
emergency patches after damage
zones built around natural terrain constraints

Local failure must be legible

If a line starves, floods, browns out, jams, or gets damaged, the player should be able to understand why from what is visible on screen.

Region archetypes

Different regions should encourage different industrial shapes:

mineral-rich basin
coastline refinery region
dense ruin zone with salvage opportunities
hazardous Flux-touched region
mountain or canyon region with constrained route planning

This helps ensure that a second or third factory is not merely a copy of the first.

Relationship to the rest of the game

The region layer should remain relevant after macro play unlocks.

Later, the player may visit a region to:

upgrade a specialized industrial district
repair a strategic bottleneck
secure a threatened Sync Station
add exports for orbital or frontier demand
recover after a raid, storm, or logistics collapse

Inter-Region Layer

The inter-region layer is where the planet stops being a map with multiple factories and becomes a single distributed economy.

Primary purpose

This layer is about coordination rather than direct placement. The player is no longer asking only, “How do I make this machine run?” They are asking:

which region should produce this
what should this region import instead of making itself
how much redundancy is worth the bandwidth cost
which shortages are local and which are planetary

What belongs in this layer

Typical systems:

regional specialization tags
long-distance transfer links
throughput budgeting
import and export ledgers
macro alerts for shortages and surpluses
photonic logistics infrastructure
mind control towers and semi-autonomous sectors

Desired feel

This layer should feel:

strategic
systemic
comparative
accountable

The player should feel that they are managing economic circulation rather than manually pushing items.

Key decisions

Specialization

A region should not produce everything. The player should be rewarded for deciding that one region becomes a heavy smelting basin, another becomes electronics-focused, and another becomes a logistics or defense hub.

Redundancy versus efficiency

Highly optimized planetary networks are powerful but brittle. Redundant networks are safer but more expensive.

The player should constantly choose between:

centralization for efficiency
duplication for resilience

Macro triage

Not every shortage should be solved immediately. Some shortages are symptoms, some are causes, and some are acceptable temporary sacrifices while the player prepares for orbital growth.

Information the player needs

This layer rises or falls on visibility. The player should be able to answer:

which regions are net importers or exporters
what each region is short on
which transport links are saturated
where strategic reserve stockpiles are located
which deficit is blocking orbital or frontier progress

Photonic network as a planetary milestone

The photonic network is the technological signature of this layer. It should feel like the moment a planet becomes one coordinated machine.

Its purpose is not to replace all local logistics. Its purpose is to provide a high-level transport and allocation fabric for large-scale inter-region flow.

That distinction matters:

local play remains about physical layout
inter-region play becomes about economic structure

Relationship to later scopes

The inter-region layer is what funds orbit.

If the player cannot already manage planetary surplus, then launch, station construction, and long-haul supply should feel impossible or fragile. This layer is therefore the bridge between local factory craftsmanship and true macro-industrial planning.

Space Station Scope

The space station scope is the first major shift where the player leaves the planet without leaving industry behind.

This scope should not feel like a separate genre. It is still an industrial game, but now the industrial body exists in orbit. The station becomes both a logistics mediator and a production site in its own right.

Core fantasy

The fantasy of the space station scope is:

lift industry off the planet
make orbit productive
build a machine that survives through external structure and internal order

Why the station needs two layers

The station has an outside and an inside for design reasons, not only visual reasons.

the exterior is about structural role, exchange, docking, exposure, and traffic
the interior is about manufacturing, processing, storage, and controlled industrial density

If both are collapsed into one layer, the station risks becoming either an abstract management menu or just another factory map. The two-layer model prevents that flattening.

Station role in the campaign

The station is where the player learns that logistics can no longer be solved only through local adjacency.

The player now has to care about:

launch cadence
orbital storage
docking pressure
construction sequence
what is worth producing in orbit
how surface and orbit specialize relative to each other

Main station tensions

The station scope is built around a few powerful tensions:

external expansion versus internal efficiency
exposed infrastructure versus protected manufacturing
planetary dependency versus orbital self-sufficiency
throughput ambition versus catastrophic fragility

The station should always feel like a valuable but vulnerable machine.

Station Exterior Layer

The station exterior layer is where orbit becomes infrastructure.

Primary purpose

This layer is responsible for the station as a visible, connected object in space.

It covers:

hull or frame expansion
module attachment
docking and traffic
external cargo exchange
solar arrays and exposed power systems
tether, elevator, and shuttle interfaces
vulnerability to damage and interruption

Desired feel

This layer should feel:

architectural
exposed
strategic
throughput-driven

The player should feel that the station’s shape matters because shape determines role, access, and survivability.

Key gameplay questions

where should docks be placed
how should cargo enter and leave the station
what external systems are worth armoring or duplicating
when should the player enlarge the station shell instead of optimizing current traffic
how dependent should this station remain on planetary imports

Station exterior loops

Expansion loop

identify an orbital bottleneck
add structural capacity
connect it to traffic and power
absorb the next growth threshold

Traffic loop

watch docks and cargo queues
identify overloaded ingress or egress points
reorganize approach patterns or add external handling capacity
smooth throughput between planet, station, and frontier

Exposure loop

place a critical external system
gain new throughput or energy capability
inherit new vulnerability
decide whether to harden, duplicate, or accept the risk

Exterior identity

The exterior should reveal the station’s strategic identity at a glance:

shipyard station
cargo relay station
orbital refinery station
elevator anchor station
frontier dispatch station

That identity should not be only cosmetic. It should emerge from real structural decisions.

Station Interior Layer

The station interior layer is where the orbital shell becomes an industrial organism.

Primary purpose

This layer exists to solve the question:

What does orbit produce that justifies the cost of building and feeding a station?

The answer should vary by campaign phase, but the station interior generally supports:

ship and shuttle production
high-value refinement
dense advanced manufacturing
expedition staging
specialized processing chains that benefit from orbital context

Desired feel

This layer should feel:

dense
engineered
expensive
constrained

Unlike many planetary factories, the station interior should not feel sprawling. Space is costly, and every module decision should imply tradeoffs.

Key design goals

Make orbital industry distinct

The station interior should not simply duplicate a planet factory. It should specialize in things that justify orbital existence:

advanced assembly
launch-related manufacturing
route-critical components
frontier support packages

Tie the inside to the outside

Interior planning must depend on exterior decisions. If the station exterior has poor docking, insufficient power, or weak storage interfaces, interior optimization should hit real limits.

Make module identity strong

A player should be able to think in terms like:

propulsion wing
fabrication bay
cargo spine
refinery core
drone operations deck

These identities help the station feel like a designed machine rather than a generic tile grid.

Interior loops

Production loop

define the station’s current industrial purpose
allocate module space to the required chains
connect inputs, buffers, and outputs
tune for reliability under orbital constraints

Dispatch loop

build frontier-facing goods
buffer them for mission windows
launch or transfer them to shuttles and route networks
recover and refill the station after each major dispatch cycle

Relationship to later play

The station interior becomes the industrial heart of frontier expansion.

Without a functioning station interior, the player cannot reliably:

build frontier craft
feed asteroid operations
seed new orbital footholds
support gate-building campaigns

Frontier Scope

The frontier scope is where distance becomes the main design material.

This scope covers expansion beyond the immediate planet-station loop. It includes interplanetary movement, asteroid exploitation, strategic route planning, precursor recovery, and eventually the infrastructure that makes true interstellar action possible.

Core fantasy

The fantasy of the frontier scope is:

turn empty space into usable territory
transform routes into lifelines
extract value from dangerous places
build the next foothold before the current one collapses

Why this scope must stay concrete

A common danger in large-scale strategy progression is that the game becomes too abstract once the player reaches maps of routes and systems.

This game should resist that. The frontier scope must keep route planning connected to physical operations:

mining hubs
shuttle depots
probes
stations
gate construction sites
new planetary descent preparations

The route map matters because it feeds places, not because it exists as a separate board game.

Main tensions

This scope should emphasize:

reach versus reliability
speed versus safety
extraction versus survivability
strategic ambition versus overextension

The player should always feel slightly ahead of their secure support envelope.

Route And Gate Layer

The route and gate layer is the strategic skeleton of frontier play.

Primary purpose

This layer is about deciding how movement should exist at large scale.

It includes:

route creation
traffic prioritization
corridor defense
gate placement
long-haul supply decisions
strategic network topology

Desired feel

This layer should feel:

strategic
high-consequence
graph-like but not abstract

The player should feel that every new route commits them to a maintenance burden and a defense burden, not just a convenience upgrade.

Key questions

which corridor is worth securing first
which gate pair is worth the investment
which station should become a major relay
when is a long vulnerable route acceptable
how much redundancy should the strategic graph contain

Gate logic

Gates should not erase logistics. They should reconfigure it.

They introduce:

focal points of traffic
infrastructure worth defending
route compression at high capital cost
new failure modes if instability or sabotage affects the network

Strategic network archetypes

Different players might shape very different frontier graphs:

hub-and-spoke empire
resilient mesh with redundancy
narrow spearhead toward rare resources
heavily fortified stabilizer corridor

The route layer should support these different doctrines.

Frontier Operations Layer

The frontier operations layer is where strategic routes terminate in actual work.

Primary purpose

This layer handles the operational exploitation of distant space:

asteroid prospecting
asteroid mining
precursor site probing
anomaly investigation
new station seeding
logistics support for planetary descent and colonization

Desired feel

This layer should feel:

risky
sparse
improvised at first
increasingly industrial over time

The first frontier footholds should feel fragile. Only later should they begin to resemble mature industrial districts.

Main gameplay loops

Prospecting loop

scan a target field or anomaly
decide whether it is worth committing assets
send probes or light craft
upgrade the site into a real operation if the return justifies it

Extraction loop

establish a small forward operation
secure cargo transfer
increase throughput without collapsing reliability
bring the site into the larger network

Colonization loop

use orbital or asteroid footholds as staging grounds
assemble the infrastructure for a more permanent presence
bridge the gap between expedition and settlement
convert a remote outpost into a new strategic anchor

Flux and danger

The frontier operations layer is where strange physics should be most palpable.

This is the right layer for:

Flux crystal extraction
containment events
precursor artifacts with unstable behavior
damaged routes causing isolation
high-value but dangerous opportunities

The player should never feel fully safe here, only increasingly capable.

Elemental Scope

The elemental scope is the final inversion of the game’s structure.

For most of the campaign, expansion means going outward:

from one machine to a factory
from a factory to a region
from a region to a planet
from a planet to orbit
from orbit to routes, asteroids, and distant systems

Then the game turns.

The player discovers that Dark Flux cannot be fully stabilized only from astronomical distance. Flux can be harvested, contained, and routed at macro scale, but true repair requires direct intervention at the level where matter itself is becoming unreliable. The answer is not to go farther out. The answer is to go impossibly far inward.

This scope begins when the player captures raw Flux, returns it to Earth, and builds a shrinking apparatus capable of inserting their embodied mind into an elemental operating environment. There, stabilizers are no longer planetary megaprojects alone. They become microscopic or atomic precision structures that restore order from the bottom up.

Core fantasy

The fantasy of the elemental scope is:

descend into the fabric of matter
treat atoms and fields as industrial terrain
repair reality through construction at the smallest meaningful scale
prove that the final answer to cosmic collapse is not only bigger infrastructure, but deeper precision

Why this scope belongs in the game

This twist works because it mirrors the whole campaign.

The game has already taught the player that:

order can be built
logistics can be scaled
instability can be contained
structure matters at every level

The elemental scope takes those lessons and reframes them:

belts become channels
regions become lattices
route planning becomes field propagation
megaproject stabilization becomes atomic repair

This is not a new game. It is the same game translated into a radically different physical scale.

Two layers

The elemental scope has two layers:

the lattice layer, where the player builds local stabilizer structures and manipulates matter arrangement directly
the flux field layer, where the player manages energetic propagation, resonance, and how stabilization spreads through larger structures

Together, these layers let the player solve both local atomic construction and larger-scale elemental dynamics.

Endgame function

The elemental scope should not replace the other scopes. It should consume them.

Planetary industry, orbital production, frontier extraction, and route planning all remain necessary because the player still needs:

raw Flux capture
transport and containment
power and specialized components
large-scale stabilizer deployment

The elemental scope becomes the missing inner half of the endgame. Macro stabilization holds the line; elemental stabilization makes lasting repair possible.

Lattice Layer

The lattice layer is the local operational layer of the elemental scope.

Primary purpose

This layer is where the player enters matter as buildable terrain.

The player is no longer laying out smelters or shuttle bays. They are arranging:

atomic anchor points
stabilizer nodes
resonance channels
containment meshes
repair scaffolds

The important feeling is that matter itself has become the factory floor.

Desired feel

This layer should feel:

precise
fragile
strange
intensely consequential

At planetary or orbital scale, a design flaw can waste throughput. At elemental scale, a design flaw can destabilize a whole repair sequence.

Core loops

Atomic construction loop

enter a destabilized material region
scan for fracture patterns or Flux contamination
place anchor structures
bridge them into a stabilizing local pattern
verify that the pattern holds under field stress

Repair loop

identify where matter rules are slipping
isolate the damaged lattice
rebuild a trustworthy structural pattern
connect it to larger stabilizer systems

Design constraints

Local readability still matters

Even though this layer is abstracted and unusual, it still needs the same clarity principles as factory play:

visible flow
visible stress
visible bottlenecks
visible failure propagation

The player must still feel like a builder

This layer should not become a puzzle game detached from the rest of the campaign. The player still places, routes, reinforces, and scales.

Relationship to macro play

The lattice layer should matter because it determines whether macro stabilizer projects truly work.

Large-scale infrastructure may hold Flux back temporarily, but only well-constructed lattice repairs create durable recovery.

Flux Field Layer

The flux field layer is the macro layer of elemental play.

Primary purpose

If the lattice layer is about local atomic construction, the flux field layer is about how stabilization spreads, resonates, amplifies, or fails across broader energetic space.

This layer handles:

field propagation
resonance tuning
stabilization coverage
interference management
coupling between local repairs and larger structures

Desired feel

This layer should feel:

dynamic
systemic
invisible made legible

The player should feel that they are operating on patterns and forces rather than on solid machinery, but the decisions should still be industrial in spirit.

Key questions

where should stabilization pressure be concentrated
which repaired lattice zones should be linked first
what field harmonics cause reinforcement versus collapse
how much raw Flux can be processed safely through one network

Main gameplay loops

Propagation loop

establish local lattice stability
route field energy through the repaired region
measure where resonance strengthens or destabilizes neighboring zones
adjust topology and tuning until repair spreads reliably

Harmonic management loop

capture and feed raw Flux into the device chain
translate it into usable stabilization potential
prevent overload, inversion, or runaway instability
maintain a field configuration long enough for repairs to become self-supporting

Why this layer matters

Without the flux field layer, the elemental scope would remain too local and puzzle-like. This layer gives the fourth scope its own strategic dimension, just as the inter-region, station exterior, and route layers give strategic shape to the earlier scopes.

It is the field layer that turns atomic repair into a campaign-scale answer.

Campaign Progression

This progression keeps cloning and mind replication late and rare while making embodiment and industrial growth central from the first hour.

The campaign repeatedly alternates between intimate operation and expanded oversight. The player masters one layer, then earns the next layer that coordinates it.

Caveat: exact numeric thresholds remain unspecified and should be tuned through playtesting.

Progression table

Phase	Scope / layer	Story beat that motivates it	Explicit unlock condition	Decisions that matter	Primary risks
One Mind / One Robot	Planetary / region	Awakening; hands returned to matter	Start state	Base location; early ore priorities	Death resets to arrival snapshot before sync
Early robot specializations	Planetary / region	A mind, many shells	Build Chassis Bay	Which chassis to inhabit and when to swap	swap vulnerability; travel time
Primitive factories	Planetary / region	Stupidity that works	Basic belts, inserters, furnaces, assemblers	topology and modular habits	bottlenecks; overproduction; weak power
Electronics + Sync	Planetary / region	Anchor the self	Produce microchips; build Mind Sync Station	sync frequency vs exploration greed	rollback loss
Smart industry + pull rails	Planetary / region	Demand becomes language	Smart module research	upgrade critical lines or rebuild cleanly	logic mistakes and silent starvation
Drone towers	Planetary / region	Hands without minds	Drone Control Tower	where drones replace fixed logistics	high power draw; congestion
Mind control towers	Planetary / inter-region	Presence without walking	Higher-tier comms and compute	which bases become semi-autonomous sectors	signal limits; reduced direct oversight
Planetary photonic network	Planetary / inter-region	Continents become one factory	Beacon construction and transmission research	regional specialization and bandwidth allocation	cascading deficits
Orbital launch and first station	Station / exterior	A second body in orbit	Launch chain and station-printing capability	what remains planetside vs orbital	fragile orbital supply
Station industrialization	Station / interior	Orbit must produce, not just receive	interior modules and industrial packages	station layout philosophy and product focus	cramped throughput and costly mistakes
Elevators, shuttles, asteroid hubs	Frontier / route plus frontier	Industry leaves home	Elevator and Shuttle Bay infrastructure	route topology; hub placement	shuttle losses; docking bottlenecks
Flux crystals and deep-belt mining	Frontier / frontier	The universe has seams	Prospecting and containment tech	risky mining vs safe scaling	rare catastrophic incidents
Portals and time dilation	Frontier / route	Distance collapses; clocks bend	Flux stabilization and precursor chronotech	gate topology; acceleration zones	instability and maintenance burden
Fragments and cloning	Frontier / route and governance	Governance of selves	Mind Replication Chamber and strict prereqs	whether to fork at all; permissions	rogue clone emergence
Dyson swarms and stabilizers	Strategic endgame across macro scopes	Star-scale power; hold the line	megaproject chains	which stars and systems to prioritize	losing regions and routes to Flux pressure
Raw Flux capture and return to Earth	Frontier to elemental transition	The enemy can be carried home as a cure or a catastrophe	Safe capture, containment, and transport chain	where to harvest; how much to risk transporting; what returns to Earth	containment failure; strategic overreach
Shrinking device and first elemental descent	Elemental / lattice	Go inward to repair what scale alone cannot	Build the elemental descent apparatus on Earth	when to commit to descent; which material zones to repair first	unstable insertion; failed anchoring
Elemental stabilizer networks	Elemental / lattice and field	Hold the universe together from the inside	Atomic anchor technology and flux-field tuning	local repair order; field harmonics; macro-to-micro resource allocation	cascading resonance collapse

Pacing logic

Early campaign

The first hour should establish:

embodiment as a real mechanic
local automation as the core fantasy
danger before sync
the fact that industrial growth is the only path out of fragility

Mid campaign

The middle of the game should be dominated by:

smarter logistics
regional coordination
the transfer from local mastery to macro responsibility
the shock of orbital expansion

Late campaign

The late game should shift from optimization toward strategic doctrine:

where to expand
what to defend
what to risk
how much autonomy to grant fragments or clones
how much infrastructure to commit to stabilizing threatened space
when to divert macro-industrial capacity into elemental repair

Solar-system emphasis before portals

The pre-portal interplanetary phase should be long enough to matter.

This is the crucial bridge between local factory simulation and large strategic routing. It teaches the player to think in:

schedules
hubs
queueing
route resilience
external supply dependency

The space elevator and shuttle era should feel like the last purely industrial answer before reality-bending technologies appear.

Final inversion: bigger to smaller

The campaign should end on a structural reversal.

The player spends most of the game expanding:

local to regional
regional to planetary
planetary to orbital
orbital to frontier
frontier to star-scale stabilization

Then the game reveals that scale alone cannot finish the work. Raw Flux must be captured, returned, and understood deeply enough for the player to enter an elemental operating environment. The final answer is therefore not simply a bigger machine. It is a smaller one, supported by all the bigger ones.

Progression flowchart

flowchart LR
  A[Awakening: one mind in one primitive robot] --> B[Chassis Bay: early specialized bodies]
  B --> C[Primitive factories: belts, inserters, assemblers]
  C --> D[Electronics: microchips and sensors]
  D --> E[Mind Sync Station: backup synchronization]
  E --> F[Smart industry: demand-aware machines]
  F --> G[Pull rails: routed mixed-item conveyors]
  G --> H[Drone Control Towers: mindless logistics swarms]
  H --> I[Mind Control Towers: remote regional operation]
  I --> J[Planetary photonic network: beacon logistics]
  J --> K[Orbit: space station production modules]
  K --> L[Solar system logistics: elevators + shuttles + asteroid hubs]
  L --> M[Asteroid mining: Flux crystals discovered]
  M --> N[Portals: interplanetary gates mature]
  N --> O[Time dilation: precursor chronotech fields]
  O --> P[Late mind events: fragments, rare cloning]
  P --> Q[Dyson swarms: star-scale power]
  Q --> R[Flux Stabilizers: macro containment network]
  R --> S[Raw Flux captured and returned to Earth]
  S --> T[Elemental descent apparatus built]
  T --> U[Elemental stabilizer networks repair matter]

Systems: Mind And Embodiment

Mind Disk embodiment

The player controls one robot body at a time by inserting the Mind Disk into a chassis. This should not be treated as a gimmick. It is the foundation of identity, risk, and scale.

Early specializations make embodiment immediately meaningful:

the miner is good at extraction
the hauler is good at transport
the builder is good at placement and repair
the scout is good at distance and sensing
combat and salvager frames widen the game later

The important emotional effect is that the player learns they are not any one body. They are continuity inhabiting hardware.

Backup disk and synchronization

The backup disk is inert until the player builds a Mind Sync Station.

The station copies a snapshot of the current mind-state into the backup. Destruction of the active body then triggers reboot from the most recent synchronized state rather than full campaign loss.

This gives saving a diegetic meaning:

before sync, progress is existentially fragile
after sync, continuity is engineered rather than assumed

Sync friction

Synchronization should remain strategically meaningful.

Requirements can include:

physical presence at a sync station
stable power
a vulnerability window during sync
later upgrades that reduce friction without removing it entirely

The core decision is whether to push deeper into danger or return to anchor continuity first.

Mind fragments

Mind fragments appear late and should feel powerful but bounded.

A fragment is a limited-scope instantiation designed to run a tower, district, or subsystem. It can optimize within assigned policies, but it should not have unrestricted sovereignty.

Possible limits:

cannot begin new research branches
cannot authorize replication
cannot redefine top-level doctrine
can execute local scheduling and operational decisions

Fragments let the player externalize cognition while keeping the original self central.

Cloning

Full cloning is a late, rare, opt-in mechanic.

It should create real strategic and ethical tension:

shared origin snapshot
divergence over time
policy and permission management
possible disagreement in priorities

The important rule is that cloning should not be a simple upgrade path. It is a governance mechanic with upside and risk.

Rogue clone risk

Rogue clones are not random. They should arise from player choice and systemic pressure:

cloning under Flux instability
insufficient governance infrastructure
permissive autonomy settings
corrupted precursor or chronotech interference

The result is a hostile industrial intelligence that uses the same verbs as the player:

mine
build
automate
route
fortify
raid

That makes the late antagonist thematically strong because it mirrors the player’s own expansion logic.

Robot roster

Chassis	Availability	Role	Strengths	Weaknesses
Primitive Worker	Start	tutorial embodiment	can mine and build minimally	slow; fragile; low carry
Miner	Early	ore extraction	high mining rate; hard-node drilling	poor carry; slower movement
Hauler	Early	transport	high carry; fast relocation	poor mining and building
Builder	Early	construction	rapid placement and repair	weak mining; low carry
Scout	Early	exploration	strong sensors; speed	fragile; low combat
Combat	Early to mid	defense and escort	weapons and armor	poor industrial efficiency
Salvager	Mid	ruins and hazardous recovery	bonus salvage; hazard resistance	specialized; slower

Memory Constructs

Blueprints become Memory Constructs, stored patterns inside the Mind Disk’s cognitive library.

This keeps blueprints diegetic:

capture an area
encode the pattern
redeploy it through a builder body or later construction drones
optionally parameterize the construct by throughput or material tier

This system reinforces the core identity of the game: the player is not merely placing objects. The player is carrying industrial memory forward.

Systems: Industry And Logistics

Industry as the main progression language

Factories are the central expression of growth in this game. Combat, exploration, survival, and narrative discovery all feed back into industrial capacity.

The player should feel that every major capability in the campaign is manufactured into existence.

Local production grammar

At the region level, the player interacts with the familiar and necessary language of automation:

extraction
smelting and processing
assembly
buffering
routing
power balancing
maintenance and repair

The early factory should already contain the DNA of everything that follows.

Three logistics families

The game’s logistics evolve into three complementary families rather than one straight-line upgrade path.

Belts

Belts are foundational transport:

high visual clarity
strong throughput
immediate physicality
good for bulk material movement

They are simple, reliable, and easy to reason about locally.

Pull rails

Pull rails are addressable routed conveyors:

shared track space
demand-aware sinks
routing logic for mixed cargo
more modular factory architecture

They live between belts and drone networks. They are more flexible than pure belts without becoming completely freeform.

Drone networks

Drone towers command mindless drones for source-to-sink work.

Best uses:

awkward terrain
flexible supply
construction support
highly dynamic delivery cases

Main tradeoff:

they consume significant power
they create congestion around towers and charging nodes

Comparative table

System	Throughput	Latency	Build cost	Operating cost	Best use	Weakness
Push belts	High, lane-bound	Low and steady	Low	Low	bulk ore and plates	routing complexity and refactor pain
Pull rails	Medium to high	Medium	Medium	Medium	modular mixed-item networks	bad logic can starve systems quietly
Drone networks	Medium and scalable	Variable	Medium to high	High	flexible delivery and construction	power hunger and hub congestion

Regional and continental logistics

The inter-region planetary layer is not just a bigger transport map. It is where the player begins to think in specialization and macro accounting.

Important mechanics at this layer:

region tags for natural resource bias
regional specialization choices
long-haul transport bandwidth
visible import and export ledgers
alerts for systemic deficit conditions

Example:

A coastal region may become the center of chemical refining, while an inland mineral-rich region becomes a heavy smelting zone. The player then has to solve the movement problem between them and decide what level of redundancy is worth paying for.

Planetary photonic logistics

Once photonic beacons exist, continents become one industrial body.

This layer should introduce:

item-class bandwidth allocation
regional throughput priority
map-level resource pressure indicators
fast diagnosis of deficits and saturation

The macro logistics layer should feel like a natural extension of factory thinking, not a separate strategy game pasted on top.

Construction at scale

The industrial game changes once the player can deploy larger plans quickly.

Memory Constructs, builder chassis, and later drones should support:

repeated factory blocks
standard station modules
regional expansion kits
repair and rebuild workflows after attacks or accidents

The player should gradually stop solving layout problems one machine at a time and start solving them through design standards and replication.

Systems: Space, Combat, And Flux

Orbital industry

Once orbit is unlocked, the station becomes the logistics brain and industrial hinge of the solar system.

The station exterior manages:

docks
solar arrays and exposed power infrastructure
cargo interfaces
shuttle traffic
structural expansion

The station interior manages:

production sectors
module internals
fabrication of rockets and shuttles
refined industrial chains
internal logistics and storage

The station should feel like an industrial body with a skin and organs rather than a menu-driven abstract hub.

Shuttle-based asteroid mining

The pre-portal frontier is built around shuttle logistics.

Typical loop:

Prospect an asteroid field.
Build or assign mining shuttles.
Route traffic to an asteroid hub.
Transfer cargo to a station refinery or depot.
Return refined cargo to orbital or planetary destinations.

This is a critical learning phase because it teaches the player to reason in route topology, docking capacity, travel time, and resilience.

Space elevators

Space elevators are the major pre-portal logistics fantasy.

They should function as extreme infrastructure that links surface industry with orbital stations continuously rather than through only disposable launch events. That makes them distinct from rockets and gives the mid-late game a strong identity before gates appear.

Key gameplay implications:

immense throughput potential
heavy infrastructure commitment
exposed strategic vulnerability
clear importance of endpoint stability

Combat and encounters

Combat should be optional early and systemic later. It should feel like a consequence of industry, territory, and escalation rather than a separate game mode.

Encounter families:

Precursor guardians Fixed defenses protecting ruins and valuable technologies.
Flux phenomena Environmental events that disrupt logistics, computation, or structural reliability.
Rogue minds Late-game industrial rivals born from dangerous choices or systemic corruption.

The most interesting combat pattern is one where supply chains feed defense and logistics failures weaken military capability.

Flux as systemic pressure

Dark Flux should express itself mechanically through instability rather than monster-like behavior.

Possible effects:

computation noise
logistics disruption
material degradation
temporal anomalies
corruption of experimental infrastructure

Flux should become more relevant as the player reaches farther and relies on more delicate systems.

Flux crystals and chronotech

Flux crystals are not just another ore. They are the point where the universe stops being merely large and becomes strange.

They justify:

containment mechanics
precursor-compatible technologies
portal stabilization
later time manipulation systems

They should be high-opportunity, high-risk resources that transform strategic options rather than simply increase output.

Raw Flux should become the key transition material between macro stabilization and elemental repair. It is not enough to power larger projects; it becomes the material and energetic bridge that makes the fourth scope possible.

Portals and route-making

When portals appear, they should not trivialize logistics. They should redefine it.

Important decisions:

where gates are worth building
which routes deserve hard infrastructure
how to defend gate-linked systems
what degree of instability is tolerable

The player should still be making industrial choices, just now at strategic graph scale.

Elemental stabilization

At the end of the campaign, the player learns that Dark Flux cannot be fully defeated only by building larger structures around it. Large stabilizers can slow collapse, route pressure, and protect whole regions of space, but they do not by themselves restore matter at the level where physical law is slipping.

That leads to a new endgame chain:

harvest and contain raw Flux
return it to Earth or another secure core world
build a shrinking and insertion device
descend into an elemental operating layer
construct local stabilizers and field harmonics that repair reality from within

This is the late-game twist that makes the campaign complete.

Endgame infrastructure

Dyson swarms, macro Flux Stabilizers, and elemental stabilizer networks justify the true endgame.

By this point, factories have become civilizational weapons:

stars are exploited as power sources
stabilizer networks become the defense line against regional collapse
elemental stabilizer lattices turn temporary defense into lasting repair
route choice determines who survives

The endgame should feel like the culmination of every earlier lesson about throughput, specialization, power, and risk.

Interaction Model And UX

The interaction model should follow the scope framework rather than fight it.

The game does not merely have camera zoom levels. It has eight operational layers, grouped into four scopes. The UI should make moving between those layers feel natural and consequence-driven.

Scope 1: Planetary

Region layer UX

Core verbs:

place machines
connect logistics
balance ratios
manage power
inspect local bottlenecks

Important tools:

throughput overlays
congestion overlays
starve and flood warnings
one-click path tracing for belts and pull rails
clear embodiment and chassis state indicators

Inter-region / continental UX

Core verbs:

inspect deficits
assign specialization
move goods between regions
diagnose planetary bottlenecks

Important tools:

regional import and export ledger
bandwidth and priority controls
visible regional role labels
shortage propagation alerts

Scope 2: Space station

Exterior UX

Core verbs:

place and upgrade exterior modules
monitor docks and orbital traffic
assess external power and cargo throughput
manage exchange with planets and frontier routes

Important tools:

station silhouette or hull planner
docking state panel
orbital traffic overlay
exposed infrastructure warnings

Interior UX

Core verbs:

design station production
manage module interiors
build rockets and shuttles
tune high-value manufacturing lines

Important tools:

persistent station sidebar
fast switch between interior sectors
internal transport overlays
queue and capacity panels for shipyard production

Scope 3: Interplanetary frontier

Route and gate UX

Core verbs:

create routes
assign trade flows
place gates
monitor strategic graph health

Important tools:

route planner view
gate network map
per-link risk and capacity visibility
Flux front proximity overlay

Frontier operations UX

Core verbs:

prospect and mine asteroids
probe anomalies
establish outposts
stage new orbital footholds

Important tools:

asteroid hub panel
hazard and integrity indicators
expedition readiness status
colonization staging checklist

Scope 4: Elemental stabilization

Lattice layer UX

Core verbs:

scan atomic fracture patterns
place stabilizer anchors
connect local repair meshes
verify structural integrity under stress

Important tools:

local lattice stress overlay
contamination and fracture map
anchor stability indicators
repair propagation preview

Flux field layer UX

Core verbs:

tune harmonics
route stabilization pressure
observe resonance spread
prevent overload or inversion

Important tools:

field-flow visualizer
harmonic tuning panel
resonance conflict warnings
macro-to-micro coupling display

Global UX principles

1. One consistent guidance channel

Tutorial and hint systems should not fragment by scope. The player should feel that they are learning one coherent game, not eight partially connected interfaces.

2. Persistent top-level context

A global top bar should remain visible across layers and expose:

active mind location
sync status
critical alerts
current logistics emergencies
priority construction or research tasks

Clicking an alert should move the player to the correct scope and highlight the source of the problem.

4. Scale should preserve accounting

When the player moves from a region to a continent, or from a station interior to a solar route map, resource logic should remain legible. The UI should never make the simulation feel like it changes rules when the camera changes context.

Hotkey concept

A simple first pass:

1: region layer
2: inter-region layer
3: station exterior
4: station interior
5: route and gate layer
6: frontier operations layer
7: lattice layer
8: flux field layer

The exact mapping can change, but the conceptual rule matters: each operational layer should be reachable directly, and the player should not feel lost while moving between them.

Narrative Integration And Agency

Narrative triggers should unlock mechanics as consequences rather than as arbitrary checklist rewards.

Unlock philosophy

Electronics unlock after meaningful precursor analysis, because stable advanced computation is discovered, not simply crafted on schedule.
Mind Sync unlocks when continuity becomes a dramatic and mechanical problem the player urgently wants to solve.
Pull rails unlock when demand-aware routing becomes intelligible inside the fiction.
Drone towers unlock when scale makes manual hauling irrational.
Space elevators unlock when rockets are insufficient for sustained industrial throughput.
Time dilation unlocks only after chronotech discovery makes it believable and dangerous.
Elemental descent unlocks only after the player proves they can capture raw Flux safely enough to bring the problem home and work on it at atomic scale.

Player choices should have systemic meaning

The player should not only choose production layouts. They should also choose doctrine.

Examples:

reckless cloning can create internal rivals
heavy time acceleration may attract or intensify Flux pressure
preserving precursor sites may slow progress but improve safety and understanding
stabilizer placement choices determine which systems remain defensible
deciding when to shift effort from macro stabilizers to elemental repair determines whether survival becomes true recovery

Agency themes

The player’s agency should widen in a controlled way:

first over a body
then over a base
then over multiple regions
then over stations and routes
then over fragments and strategic territory
then over the smallest structures that keep matter coherent at all

This widening must always feel earned through infrastructure rather than granted by abstract authority.

Core thematic tension

The game should repeatedly ask:

How much of yourself are you willing to externalize?
How much autonomy can you safely grant?
How much instability will you tolerate in exchange for speed?
Which places are worth saving when not everything can be saved at once?

That tension keeps the game from becoming only a throughput puzzle. It turns industrial expansion into a meaningful expression of identity and responsibility.

References And Inspirations

This project sits at the intersection of factory-game UX, transhumanist identity fiction, and hard-science-inspired megastructure imagination.

Factory and automation references

Factorio Useful for transport legibility, industrial escalation, and onboarding lessons.
Factorio Wiki Useful for belts and logistics-network framing.
Dyson Sphere Program Useful for galaxy-scale industrial ambition and star-scale growth fantasy.
Satisfactory Useful for embodied factory construction and exploratory industrial play.
Mindustry Useful for the fusion of production chains, pressure, and defense.

Technical and conceptual references

Sandberg and Bostrom, Whole Brain Emulation: A Roadmap Useful for mind instantiation and continuity framing.
Shulman, WBE and the Evolution of Superorganisms Useful for fragments, copying, and governance themes.
Dyson, Search for Artificial Stellar Sources of Infrared Radiation Useful for Dyson-swarm framing.
Kardashev, Transmission of Information by Extraterrestrial Civilizations Useful for energy-scale framing.
NASA Smitherman, Space Elevators Useful for geostationary elevator grounding.
NIAC Edwards papers Useful for tether concepts and materials inspiration.
NIST and ESA relativity references Useful for grounding time-dilation motifs.