Selene trains a coordinated fleet of rocket-powered hopper drones to explore the uncharted far side of the Moon during the two-week lunar night. With no direct Earth line-of-sight and extreme cold (-170 °C), Gemini 4 Argon acts as the reasoning orchestrator: interpreting mission safety standards, generating fleet exploration plans, steering reinforcement learning, and resolving safety violations flagged by a deterministic Monte Carlo verifier.
Concept render: 4-hopper fleet trajectory verification, automated hazard rerouting, and coordinated touchdown.
The far side of the Moon never faces Earth, ruling out direct teleoperation. During the lunar night, ambient temperatures plunge below -170 °C and solar power drops to zero.
Selene addresses this via a hybrid autonomy architecture:
- Multi-Hopper Fleet: Four autonomous hoppers disperse from a central lander hub to survey permanently shadowed craters, take surface scans, and share battery resources.
-
Deterministic Physics Simulator: A vectorized dynamics engine evaluated on real NASA LOLA 100 m elevation models (SLDEM2015) simulating lunar gravity (
$1.62,\text{m/s}^2$ ), rocket propulsion, thermal losses, and orbital relay pass windows. - World Model & MAPPO: Multi-Agent PPO with centralised training and decentralised execution (CTDE), augmented by an ensemble world model for transition prediction.
- Argon Orchestrator: Gemini 4 Argon acts as mission commander—generating structured JSON plans, diagnosing failure logs, and modifying trajectories when verifier constraints fail.
- Monte Carlo Verifier: Fast, non-differentiable safety gates running 1,000 perturbed rollouts per plan to certify landing slopes, collision buffers, fuel reserves, and TDMA relay exclusivity.
Before any trajectory is uplinked, Argon evaluates fleet dispersion across target craters. If any hopper encounters hazardous terrain (e.g., rim slopes
During an extended 30-minute training benchmark on the real NASA LOLA Daedalus crater dataset (15,790,080 transitions over 4,112 updates), the fleet demonstrated strong convergence and collision-free coordination:
| Metric | Initial Policy | Converged Policy | Improvement |
|---|---|---|---|
| Mean Episode Reward | 131.36 | 539.88 | +311% |
| Crash Rate | 0.0000 | 0.0000 | Zero crashes maintained |
| Crater Overlap Rate | 4.76 | 1.90 | -60.1% (better dispersion) |
| Relay Comms Conflicts | 2.11 | 0.0156 | -99.3% conflict resolution |
| World Model Error (MSE) | 1.3599 | 0.0137 | -99.0% error reduction |
| Verifier Monte Carlo Safety | 92.0% | 100.0% | Certified flight-ready |
The environment implements lunar flight dynamics and environmental constraints:
Each sub-orbital hop is modelled as an impulsive burn at elevation angle
where
Propellant mass consumption
where
Power consumption during the lunar night combines avionics baseline draw, survival heating in deep shadow, and science sensor active bursts:
Landing on terrain with local slope
Selene is fully reproducible with clean single-command scripts using uv:
git clone https://github.com/Nabzx/selene.git
cd selene
cp .env.example .env # Add GEMINI_API_KEY (optional for offline cached runs)# Sim physics, reward, MAPPO, and verifier tests
(cd apps/sim && uv run pytest)
# Argon agent schemas, tools, and orchestrator tests
(cd apps/agent && uv run pytest)Execute the full autonomous mission loop (Safety Spec
./scripts/mission_pipeline.sh(Or run ./scripts/run_demo_pipeline.sh for the non-interactive 5-phase batch check.)
cd apps/sim
uv run python -m selene_sim.mappo \
--terrain data/terrain/daedalus_nasa_sldem2015.npz \
--updates 500 \
--checkpoint-dir data/checkpointscd apps/sim
uv run python -m selene_sim.verifier \
--plan ../../data/fleet_plan_revised.json \
--rollouts 1000 \
--terrain data/terrain/daedalus_nasa_sldem2015.npzselene/
├── apps/
│ ├── sim/ # Vectorised Moon sim, NASA DEM loader, MAPPO, World Model, Verifier
│ └── agent/ # Gemini 4 Argon orchestrator (tools, schemas, agent harness)
├── data/
│ ├── terrain/ # NASA LOLA DEM crops (Daedalus crater 20 km x 20 km)
│ ├── checkpoints/ # Trained policy checkpoints
│ └── runs/ # Benchmark telemetry logs and episode datasets
├── docs/ # Research notes, collaboration workflows, ADRs, run logs
└── scripts/ # Pipeline runners and visual generation scripts


