gatOS has a large implemented surface. It also has an unusually honest validation record: code and game-free tests can be complete while a feature still needs its first real KSA flight. This page keeps those two facts separate.
The current audited KSA baseline is 2026.8.5.5168. A later 2026.8.19.5261 upgrade has green build and test coverage, but its game-bound re-verification checklist remains open. The full record is maintained in docs/VALIDATION.md.
The transport plumbing has been exercised with a real guest. Flight behavior still needs its in-game checklist.
Validation: Guest and automated integration coverage is green; the broad live KSA pass remains open.
MCP is a loopback-only logical JSON API for agents, not a filesystem mirror.
Gate: mcp_enabled = true
Validation: Schema and static coverage are complete; the live mod lifecycle pass remains open.
The Kitty image stream is intentionally a terminal feature and is excluded from MCP v1.
Gate: display_enabled = true
Validation: An informal in-game pass succeeded; the formal stream and soak checklist remains open.
These are shipped surfaces with real gates and limits. Treat a first flight as a friendly test mission.
Gate: camera_enabled, audio_enabled, schedule_enabled, or debug_namespace
Validation: Code and game-free tests are complete; their dedicated live-flight checklists remain open.
IVA physics starts disabled and does no work until you enable it.
Gate: debug_namespace = true, plus feature-specific gates where noted
Validation: Code is complete; KSA render and physics behavior still needs a live-flight pass.
The virtio serial bridge is the supported hardware-style channel today.
Gate: bus_ccsds / bus_1553
Validation: Configuration placeholders exist, but neither bus is served yet.
The following are the live-flight passes still called out by the maintained record:
| Area | What remains to prove | Checklist |
|---|---|---|
| Core terminal and game integration | purrTTY session lifecycle, mount, telemetry, control, and KSA hooks | T6.6, T9.3 and G1-G4 |
| MCP | listener lifecycle, local client discovery, game-thread commands, and boundaries | MCP transport |
| Terminal video | capture, terminal display, resizing, multi-reader behavior, and cleanup | Screen stream |
| New KSA build | accessor health, orbit sentinels, physics-bubble welds, render paths, and IVA | 5261 re-verification |
| Creative and debug surfaces | welds, parts, force render, scale, RCS, impulse, audio, IVA, FX, scheduling, and camera | Welds, audio, IVA |
The checklists include prerequisites, expected values, cleanup behavior, and KSA-specific risks. Treat them as the detailed answer to “is this ready for my extremely ambitious mission?”
That is a status note, not a warning label on the whole project. The integration suite and game-free tests cover the transport, filesystem, parser, scheduler, and model layers. The remaining work is the part only a real spaceflight full of tiny astronauts can settle.
For the authoritative current record, use Validation,
milestones, and the
full /sim specification.