Planet Gravity

The brief, in short:

Make a planet-gravity demo: a small spherical planet the player can walk all the way around, including over both poles, with a second body nearby to jump across to. Keep it mathematically spherical, no hidden world-up assumptions. Third-person, single player, with a camera that stays comfortable through the pole crossings.

Airogel has no native radial gravity, so the agent wrote it. The controller computes the surface normal from the planet centre every step, projects input into the tangent plane, integrates at a fixed 120 Hz, and carries the player's heading across the surface with the minimal rotation between normals so there is no singularity at the poles. The handover to the second planet happens only in flight, once the other surface is clearly closer.

• The crater surfaces are procedural vertex and fragment shaders written for the demo.
• The EVA suit, the outpost equipment, the survey pedestals and the beacons are primitives placed by a deterministic Python dressing generator, so the scene can be rebuilt from its manifest.
• The camera is fully scripted, filtering its up vector separately from the character so the player's chosen heading survives both poles.

It verified trajectories with the editor's physics simulation (a full meridian circuit and a round-trip transfer are recorded as evidence), kept a Lua harness for the controller, and filed three support tickets. One asked for native radial gravity and is still open. Another, about bloom turning the viewport black in Safari, was fixed in the engine the same day.

Missions (29 October, release 6). The follow-up brief asked for more worlds and something to do on each. The agent split the single combined scene into five: a mission-control menu built from native flowing GUI panels, and four mission scenes that each load only their own environment plus the shared astronaut, star field and HUD.

• The shared controller reads its mission and menu scene from variables on each scene's camera, so one script serves four gravities: a held jump reaches about 7.5 metres on Vesper and under 2 on Pyra.
• Mission types are survey and extraction, sequential relays, recovery and delivery, and a stand-still scan. Badges, best times and the last selection are saved on the device through game storage.
• Decorative primitives are collider-free and share geometry and materials for automatic batching, lights are budgeted to four per scene, and signal glow is emissive, following the renderer guidance.

It generated the scenes and their menu scripts from manifests, ran 2,740 controller checks including pole circuits at three frame rates and both transfer directions, 19 menu navigation cases, and a structural audit of the deployed scenes read back from the server, and shipped with zero preflight warnings.