L3-CDH-SW-UPD
CRITICAL
COMMAND CONTROL
Level 3 · software
Software Update System
Autonomous Over-the-Air Software Update and Verification
System enabling autonomous software updates with verification before deployment
Purpose
System enabling autonomous software updates with verification before deployment
Context
Child of L2-CDH-SW
Principles
- ▸A/B partition scheme enables rollback if new software fails after update
- ▸Cryptographic signing prevents unauthorized or corrupted software from loading
- ▸Automated regression testing validates new software against known-good test cases
- ▸Staged rollout applies updates to non-critical systems first before critical ones
Typical implementations
- ▸Tesla OTA update architecture (adapted concept for space)
- ▸Android A/B seamless system updates
- ▸NASA software update procedures for ISS and deep space missions
Lunar considerations
- ▸100-year mission means software MUST evolve - cannot rely on initial version forever
- ▸AI-generated code updates must be rigorously verified before deployment
- ▸Update system itself must be ultra-reliable - corruption could brick the system
Specifications
Functional
| primary function | System enabling autonomous software updates with verification before deployment |
Interfaces
Provides
- Updated software images for deployment
Requires
- Storage for software images and rollback partitions
Cite this entry
Lunar Ark Codex. "Software Update System" (L3-CDH-SW-UPD). Retrieved 10 September 2026, from https://lunarark.com/entry/L3-CDH-SW-UPD
Licensed CC-BY-SA 4.0. You may reuse and adapt this entry with attribution, under the same licence.