Colony Ops is a focused cabinet about the colony operations terminal. Build and operate a colony on Kestrel-9b: power, air, water, morale, and the occasional emergency. It belongs to the Spacefront Wing floor because it turns a subject from the Spacefront library into a short, repeatable decision loop. You can play without an account or installation, then return to the page to read the reasoning behind the mechanics.
How to play
Start with the default state and read the screen before making a change. The cabinet uses mouse, keyboard, touch controls, but the important control is the question you ask yourself before the next action: what is the system telling me, what am I trying to change, and what will this choice make harder? Keep the system balanced while the situation changes. A colony, flight, or picket line is a chain of dependent resources, so a local win can be a global problem if it consumes the margin another subsystem needs.
The first run is for orientation. Notice which values move together, which action has a cost, and what the end screen remembers. On the second run, choose one deliberate priority. Do not try to improve every measure at once; a clear constraint makes the result easier to interpret. If the cabinet offers a pause, inspection, journal, or replay step, use it. Those are part of the lesson rather than friction around it.
What the simulation actually models
The model is a coupled system. Power, air, water, morale, vehicle state, mission goals, or defensive coverage influence one another, so the cabinet rewards reading dependencies rather than optimizing one meter in isolation.
The cabinet is not a forecast, certification, clinical assessment, engineering design, or field procedure. Its value is narrower and more useful: it gives you a safe place to feel a relationship. In Colony Ops, the relationship to watch is between the player’s strategy choices and the state that follows. A run that goes badly can still teach you where the margin was, which signal you ignored, or which assumption was too broad.
A better second run
Before replaying Colony Ops, write one sentence about the previous result. “I spent the scarce action too early,” “I optimized the visible meter and starved the hidden one,” or “I treated a lead as proof” is enough. Then change one decision and leave the rest alone. This is the small experiment that turns a game over into an observation. It also makes the game a useful bridge into the longer guidebooks rather than a decorative button beside them.
How it was built
The cabinet is a small systems lab in the browser. It exposes a handful of interacting resources, records the consequences locally, and turns a complicated subject into a sequence that can be replayed with a different priority or constraint. The landing page stays separate from the playable bundle so the game can remain quick and focused while this page carries the explanation, links, and safety framing. No account is required, progress stays in the browser, and the cabinet does not ask the player to touch a real system or submit personal data.
Read the idea behind the cabinet
If you want the slower version, start with Cislunar Communications and Navigation: The Network Between Earth and the Moon and Cryogenic Propellant Storage and Transfer: Keeping Fuel Useful in Space . Read for the model, not a perfect score: the guidebooks name the evidence, constraints, maintenance habits, or human context that a short session has to compress. Then come back and try the cabinet with one of those ideas in mind.
The useful outcome is not that the game tells you what to buy, believe, diagnose, or do in an emergency. It is that the next real question becomes more precise. That is what a good learning cabinet should leave behind: curiosity with a boundary, a model you can explain, and a reason to look at the evidence again.