Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Roadmap And Deliverables

This chapter turns the concept into immediate design outputs.

First 60 minutes script

Goal: reach real automation fast while showcasing embodiment and the absence of early sync.

Suggested flow:

  • opening cinematic and awakening in primitive chassis
  • first ore to first furnace to first belt loop
  • Chassis Bay objective: build Miner, Hauler, and Builder
  • establish stable basic plate production
  • discover precursor slab and tease electronics

The player should leave the first hour understanding three things:

  • they are a mind, not a body
  • automation is the real path forward
  • death before continuity backup is meaningful

Tech tree draft

A one-page initial tech tree should include:

  • Tier 0: Chassis Bay, belts, furnaces, assemblers
  • Tier 1: power grid, basic research, sensors
  • Tier 2: electronics and Mind Sync Station
  • Tier 3: smart modules and pull rails
  • Tier 4: drone towers
  • Tier 5: mind control towers
  • Tier 6: planetary photonic beacons
  • Tier 7: orbit and station modules
  • Tier 8: elevators, shuttles, asteroid hubs
  • Tier 9: Flux containment and portals
  • Tier 10: precursor chronotech and time dilation
  • Tier 11: fragments and rare cloning
  • Tier 12: Dyson swarms and macro Flux Stabilizers
  • Tier 13: raw Flux capture and elemental descent apparatus
  • Tier 14: elemental stabilizer lattices and field harmonics

Enemy and Flux mechanics draft

Threat families to define in detail:

  • precursor defenses
  • Dark Flux events
  • rogue minds

Each family should eventually specify:

  • triggers
  • telemetry
  • counterplay
  • escalation model
  • relationship to industry and logistics

The next documents worth writing are:

  1. A detailed tech tree with narrative justification per node.
  2. A planet-scope design chapter with region and inter-region UX examples.
  3. A station-scope design chapter with interior and exterior module examples.
  4. A frontier-scope design chapter with shuttle routes, asteroid hubs, and gate planning.
  5. An elemental-scope design chapter covering lattice construction, field tuning, and macro-to-micro coupling.
  6. A save, sync, and identity document explaining rollback, backup, and clone rules.
  7. A data model for items, machines, regions, stations, routes, minds, and elemental stabilizer structures.

Long-term documentation direction

As the project evolves, this mdBook should become the place where:

  • the creative premise stays stable
  • system decisions are recorded
  • scope boundaries are clarified
  • implementation plans can later reference established design language

That way the design does not dissolve into scattered notes once production starts.