MANUAL SHELF / TWO PROPOSED FLIGHTS
Flight Manuals
These manuals organise two proposed flights by what the astronaut must know before acting. The same cockpit vocabulary serves different decisions: a landing demands a reading of motion, while a relay mission demands a reading of signal confidence. Neither manual describes a released product. Each is a working concept with a defined design question and a deliberately limited scope.
FLIGHT 01
Tin Horizon: arrive with room to correct
A shallow shelf inside the Bell Crater offers enough ground for a small lander, but its safe area narrows as the approach drifts. The proposed sequence begins with instrument checks, moves through braking and ends with a decision to commit or climb away. A radar sweep reports an observation from a moment ago. The astronaut must relate that observation to the descent needle instead of treating either instrument as a complete answer. Read the Tin Horizon dossier for the intended loop and the art direction of the capsule.
Open complete manual →FLIGHT 02
Relay Return: carry a signal home
An aging courier has lost a reliable connection to its receiving station. The pilot checks power routing, tunes the receiver and distinguishes a new response from a fading repeat. Progress depends on restoring useful information while preserving enough electrical reserve for the return. The Relay Return dossier explains how an apparently successful transmission can still leave a navigational question unresolved.
Open complete manual → Preparation is part of play
The manuals should help players form an expectation, not reveal a single winning script. A preflight check establishes which lamp belongs to which circuit and how a selector reports its position. Later, the same relationships make faults understandable. We are interested in a small collection of consistent controls rather than a wall of switches that exist only as scenery.
Recovery deserves its own chapter
Both concepts leave space for a safe retreat. A missed landing can lead to another approach; a weak connection can justify waiting for a better window. Recovery should consume something meaningful without turning a first mistake into an invisible failure. The instrument notes discuss how to communicate these costs before the player commits.