Software

Flight software and autonomy, organized by the problem the code solves rather than by the vehicle that carried it. A page belongs here if it describes something that runs, on a processor, under a real-time or downlink constraint.

The division is the one a flight software team actually uses: what the software knows about the world (localization, perception), what it decides (planning, guidance and control, multi-agent), how it survives being wrong (fault management), how it talks to the ground and to other vehicles (communications, data handling, human interaction), what it runs on (flight software), and how it is shown to work before launch (verification).

Round-trip light time sets the boundary, seconds at the Moon and hours in the outer solar system. Every technique here exists because some decision had to be made inside that window, or because the data to make it on the ground would not fit down the link.

Every page carries the cost of the technique on the hardware it ran on. A page that says a method is used, without saying what it consumed and what it achieved, is not finished.