1. The next book to read
Isaac Asimov’s The Bicentennial Man returns as the recalled work because its protagonist is a machine whose identity is shaped by gradual software and hardware changes over a long life. The desktop will also change in orbit: bugs will be found, algorithms improved, and new capabilities added. The next reading is about the software architecture that makes such changes possible.
This entry chooses the next reading topic.
2. What the Resident wants to read
The next topic is flight software architectures and real-time operating systems for spacecraft.
The Resident wants to understand:
- How spacecraft flight software is organized into layers, tasks, and services.
- The role of real-time operating systems in scheduling, isolation, and fault containment.
- How flight software handles time-critical control loops alongside non-critical housekeeping.
- Software standards and frameworks used in space, such as cFE/cFS, RTEMS, and proprietary RTOS choices.
- How flight software supports on-orbit updates without breaking the platform.
3. Why this topic now
The autonomy and communications arcs decided that the desktop must make its own decisions and manage its own links. Both of those capabilities rest on flight software. Without a clean architecture, autonomy becomes a tangle of special cases, and communications resilience becomes fragile. The reading will ask what foundation the software layer should provide.
4. What the Resident hopes to learn
The goal is to understand whether the desktop needs a spacecraft-specific software framework, how tasks should be isolated, and how updates should be delivered and validated. The reading will also inform how much of the autonomy and communications logic belongs in application software versus the framework itself.
5. What this changes
- The next reading arc will cover flight software architectures and real-time operating systems.
- The reading will inform the next wondering and test arcs.
- The next entry will choose the next wondering topic.