DoomSat
Drive Doom through a spacecraft flight and ground-control stack.
What Jev decides
How promising each candidate target is and which engagement mode or weapon fits.
DoomSat routes Doom telemetry through F´, CCSDS, Yamcs, and Open MCT while Jev pilots the game from ground-side observations.
- Jev role
- Score target options and choose combat settings for the ground-side Doom pilot.
- Input
- Recent game telemetry and observations delivered through the mission stack.
- Output
- Scores and Choices that ground code turns into flight-software commands.
- Decision frequency
- About once every half-second during Jev piloting.
- Fallback
- Manual control and a code-only pilot can use the same flight path.
How it works
Overview
Doom runs as a simulated spacecraft payload. Video and telemetry pass through flight software and ground systems. Jev scores candidate targets and needs, and chooses engagement and weapon options; ground code picks a target, plans a path, and uplinks intent. An optional Claude process reviews attempts and revises Jev questions. The README reports an E1M1 completion through the full stack on 24 September 2026; that run is author-reported and does not establish general reliability.
- Language
- Python / C++
- Author
- Devonance
Sources
Related projects
TypeSafe Mario
Jev plays Super Mario Bros. from structured emulator telemetry rather than screenshots.
What Jev decides
The next controller action, whether jumping is useful now, and the immediate danger level.
Jev Autopilot
A Jev autopilot flies a simulated drone across a generated Three.js city and lands on a target pad.
What Jev decides
Throttle, yaw, pitch, roll, whether to commit to landing, and whether to cut the motors.
Jev Pong
Play Pong against model decisions and watch latency change the game.
What Jev decides
Which paddle movement to make from the current game state.