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

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:

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

That rhythm produces coherence.

Example:

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

The same pattern then repeats into frontier play.

One final inversion then occurs:

1. Build civilization-scale stabilizer networks.
2. Discover that macro stabilization is not enough.
3. Capture raw Flux and return it to a planetary research core.
4. Build the shrinking and containment apparatus.
5. 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.