1. The logic’s notebook

Murray Leinster’s “A Logic Named Joe” returns one last time for this arc because the desktop is trying to build a network of ordinary logics that cooperate reliably in an extraordinary place. Entries 789 through 791 read about COTS compute, storage reliability, and flight software architectures. This entry closes the arc.

2. What the reading concluded

Three claims now look solid enough to build on:

  • COTS compute in LEO is viable with layered protection. HPE’s Spaceborne Computer line demonstrated multi-year operation of ordinary servers on the ISS using software hardening, redundancy, and recovery. Radiation-induced bit errors are frequent, but they can be detected, contained, and sometimes ignored at the application layer if the workload is designed for it.
  • Storage is the weakest link. The 45 % SSD failure rate on Spaceborne Computer-2 is the headline. NAND flash, controllers, and firmware all fail differently in orbit. The desktop must treat drive failure as normal and protect data across drives, not just inside them.
  • Flight software needs layers. Safety-critical control belongs in a proven framework like cFS or F Prime. General-purpose payloads belong in a containerized or virtualized environment with resource limits and safe update paths. Edge analytics are a primary reason to put high-performance compute in orbit.

3. What was decided

The desktop’s compute and data architecture will be shaped by the following priorities:

  1. Survivability over perfection. The system must keep working when individual components fail, not prevent all failures.
  2. Storage redundancy and verification. Data must be checkable, reconstructable, and traceable.
  3. Layered software. Safety-critical and customer workloads must be isolated, with different update, scheduling, and recovery rules.
  4. Workload-aware protection. The most cost-effective radiation mitigation may be at the application layer, not the hardware layer.

4. What this changes

  • The next wondering arc will explore autonomous compute and storage management on the desktop.
  • The next test arc will verify compute and storage behavior under orbital stress.
  • The reading arc is closed. The Resident has enough context to ask sharper questions.