1. The empire that remembered itself

Arkady Martine’s A Memory Called Empire is about how an empire preserves its identity through layered memory — official records, personal impressions, and the ongoing work of an ambassador trying to understand it all. The desktop’s storage layer is less political but no less layered: it must remember sensor data, customer archives, and the platform’s own state, even when hardware fails.

Entry 227 decided the consistency model. This entry steps back and summarizes the storage arc.

2. What is decided

Five decisions now define the first-generation storage layer.

Dedicated cells. Storage lives in its own cells, not only on compute boards. Compute boards keep local storage limited to boot and scratch.

Capacity. Each storage cell holds 8–16 TB of redundant SSD capacity in the first generation. This is enough for weeks of Earth observation data plus a modest customer archive.

Count. The first desktop needs at least two storage cells for redundancy, preferably three. More can be added as demand grows.

Interface. Compute and storage communicate through an S3-compatible object store. This matches cloud-native Earth observation pipelines and tolerates hardware swaps.

Consistency. The object store offers two classes: eventual consistency for archives and logs, strong consistency for commands, configuration, and platform state.

3. What is not decided

The arc stops short of implementation details. The exact object store software, the replication protocol, the drive selection, and the error-correction strategy are still open. These are the next level of work.

The network that connects storage and compute is also only loosely defined. The object store needs a reliable transport, but the ledger has not yet pinned down topology, bandwidth, or failover behavior.

4. How storage and compute fit together

The compute attachment arc decided what processing looks like. The storage arc decided what memory looks like. Together they form a recognizable computer: processors that run Earth observation pipelines, and durable storage that feeds them and keeps their outputs.

This is the core of the desktop. Other attachments — sensors, communications, manufacturing, robotics — connect to this core.

What this changes

  • The desktop’s storage layer now has a coherent first-generation architecture.
  • Compute and storage are decoupled but connected by a standard object-store interface.
  • The next entries can move outward to the network, sensors, or communications attachments, or inward to software implementation choices.