Spacecraft Emergency — the computer that refuses to guess

A stricken ship, six candidate actions, and a flight computer that knows the difference between a close call and a coin flip. Rule gates fire first — hull critical, thermal limit, the crossing gone out of range — and are never asked. Everything else is scored on the snapshot, and confidence is honest arithmetic: the score gap times sensor agreement, where every conflicting gauge quarters it. Below 0.30 the computer abstains — the sim freezes, the console shows its reason plus both readings of every disputed gauge, and you decide as the captain. The engine gets the uncertain band; if IT refuses too, that escalates as well. Refusal is a first-class outcome here, never an error.

What decides what

  • Rules fire before any question. Hull at 15 or under, a fire with a failing crew, temp at 95, or a crossing that is out of range while Earth is in range — each executes straight off the rule ladder and lands on the rule rung. A test pins each gate with its exact fixture.
  • Confidence is arithmetic, not vibes. Six actions score on the snapshot; confidence = score gap × sensor agreement, and each conflicting channel quarters the agreement. Below 0.30 the computer abstains and the sim freezes until the captain answers; 0.30–0.55 goes to the engine under the ask budget. No token → the argmax decides and the rung says so.
  • An engine refusal escalates; garbage does not. A true abstain from the engine hands the call to the captain — but a malformed answer is ignored and the argmax holds, same as every other game. Both behaviors are pinned by tests.
  • Determinism survives latency. Decision latency is stamped on each decision and kept out of the summary, so same-seed replays stay identical; sensor faults stick for ~15 s and self-heal; an empty tank cuts the engines. Twenty tests run in CI.

Honest edges

  • The captain's console can sit empty for a whole calm crossing: difficulty 0 means no random events, and with clean telemetry the score gaps stay wide. Inject a sensor fault to see the abstain ladder actually fire — the showcase is honest about when it does and does not trigger.
  • The sensor strip shows the readings the computer last decided on, not live truth — rendering never touches the RNG stream, or a repaint would desync the deterministic sim.
  • The freeze is total by design: while an abstention pends, physics stops. The captain cannot ignore a fire, and neither can you — the sim will not advance until someone answers.
  • The flight log is session-only — a checkpoint every 60 sim-seconds plus the outcome. Close the tab and it is gone; nothing leaves this page.