1. The book that rewrote itself

Neal Stephenson’s The Diamond Age returns as the recalled work because the Young Lady’s Illustrated Primer is not a fixed text; it evolves with its reader, drawing on external sources and internal state. The desktop’s software will similarly need to evolve, but its updates must be bounded, verifiable, and reversible.

This entry asks what autonomous software updates need from the desktop.

2. Storage for updates

Software updates need room. The desktop must have:

  • Staging storage: enough space to hold one or more pending updates.
  • Dual-image storage: enough space for at least two bootable images.
  • Persistent logs: records of what was installed, when, and with what result.
  • Configuration storage: a separate area for parameter tables that can be rolled back independently.

Storage must also be radiation-tolerant or protected by checksums so that an update is not corrupted before it is applied.

3. Compute and boot support

The compute layer must support:

  • Secure boot or verified boot: only authenticated images run.
  • Bootloader with fallback: the ability to select a previous image if the new one fails.
  • Module loading: the ability to load and unload applications at runtime.
  • Watchdog integration: automatic rollback if a new image hangs.

4. Operations and policy

Updates are not just a technical problem. The desktop needs:

  • A release calendar: which updates are allowed when, relative to mission phases.
  • Compatibility rules: which versions can run together across cells.
  • Test gates: updates must pass ground testing before being approved for upload.
  • Notification rules: ground must be informed of every update, success or failure.
  • Emergency override: the ability to force a rollback from ground.

5. Security

Autonomous updates are an attractive attack surface. The desktop must:

  • Authenticate the source of every update.
  • Verify integrity with cryptographic hashes.
  • Encrypt updates if the link requires it.
  • Refuse downgrades to known-vulnerable versions.

6. What this changes

  • Autonomous software update is an architecture-wide capability, not a single feature.
  • The desktop must design storage, boot, operations, and security together.
  • The next entry will close the autonomous software update wondering arc and record the decision.