Launch Terminus through daemon-owned Hangar

This commit is contained in:
Meta Vens 2026-08-08 08:45:14 +01:00
commit 152db9e744
12 changed files with 891 additions and 85 deletions

View file

@ -1,6 +1,6 @@
# Aetheria Game Modes And Progression
Status: adopted target design; shared Hangar state is not yet implemented
Status: adopted design; the first daemon-owned Hangar/Terminus deployment slice is implemented
## Product Modes
@ -177,22 +177,31 @@ a parallel gameplay path.
## Current Migration Seam
The daemon already owns typed run checkpoints, loadout templates, catalog keys,
combat, loot, docking, trade, and Terminus scenario generation. Starbridge has
typed session, station-stock, role, wave, and summary documents. These are
components of the design, not yet a durable shared Hangar owner.
The daemon now owns one typed local Hangar, its starter ship, stored equipment,
saved loadout template, Hangar revision, and immutable Terminus deployment
receipt. It publishes `aetheria.hangar` as the ordinary Unity entry surface.
The surface advertises equip, remove, launch, and continue operations. Launch
instantiates the current committed loadout into a newly identified Terminus
run; continue reopens the deployed run selected by the existing checkpoint.
Unity remains a generic Eve lowerer and never edits those documents directly.
This is the first vertical slice, not the completed cross-mode progression
machine. Settlement, currencies/unlocks, multiple owned ships, richer fitting
interaction, Starbridge admission, and Arena admission still need to enter the
same Hangar boundary. The old main-menu `New Game` writer is no longer a
product run-creation authority. Explicit Terminus proof profiles remain
verification-only inputs.
Arena does not yet have a named server/session/admission/score document family
or a preserved headless controller harness. Shared simulation smokes are useful
substrate, but they do not constitute the Arena mode. Starbridge's existing
documents also do not by themselves prove mixed-authority convergence.
The next state-architecture cut is to define the canonical Hangar, Deployment,
and Settlement documents; define one typed mode-selection boundary; and keep a
minimal Terminus, Starbridge, and Arena vertical slice alive against it. Until
that cut lands, documentation and verification must not describe existing run
checkpoints or proof scenarios as cross-mode progression authority, or generic
simulation smokes as Arena product proof.
The next state-architecture cut is to carry this Hangar and Deployment boundary
through Starbridge and Arena admission, then add exactly-once Settlement. Until
those cuts land, documentation and verification must not describe the local
starter Hangar as completed cross-mode progression, or generic simulation
smokes as Arena product proof.
## Required Proofs

View file

@ -24,10 +24,14 @@ leaving Play drops that client while the authoritative daemon remains alive and
ready for the next connection.
Starting the daemon does not create, load, or step a game world. It starts the
typed state boundary and CultMesh transport in `ready` mode. A playable-world
subscription loads an existing run. Typed mode selection chooses authority and
policy; a committed deployment/admission creates session state through the
applicable provider or Arena server. Only that activation boundary opens
typed state boundary and CultMesh transport in `ready` mode and publishes the
`aetheria.hangar` Eve surface. The Hangar exposes the canonical saved loadout
and typed equip/remove operations. **Launch** commits a Terminus deployment
from the current Hangar revision and creates its run; **Continue** selects the
existing deployed Terminus checkpoint without creating a replacement run.
Typed mode selection chooses authority and policy; a committed
deployment/admission creates session state through the applicable provider or
Arena server. Only that activation boundary opens
simulation persistence and starts the fixed simulation clock. When the last
playable-world subscription is withdrawn,
the daemon commits the final public frame and matching private Ymir checkpoint,
@ -53,9 +57,10 @@ being debugged.
1. Press **Build daemon** after changing daemon code. Use **Reimport state &
build** only when the isolated development state must be replaced.
2. Press **Start daemon** and wait for the window to report the live endpoint.
3. Enter and leave Unity Play Mode normally. The daemon remains running across
client sessions.
4. Edit and inspect the generic EveUnity-lowered world in Play Mode.
3. Enter Unity Play Mode. The generic client mounts `aetheria.hangar`.
4. Configure the saved loadout, then choose **Launch** for a new Terminus run
or **Continue** for the currently deployed saved run. The same mounted Eve
surface becomes the gameplay composition after activation.
5. Use Unity Pause to submit the advertised `simulation.pause` action to the
daemon. Unity unpause submits `simulation.rate.realtime`.
6. While paused, use **Advance one step** to commit exactly one fixed daemon