1. The three laws of a useful machine

Isaac Asimov’s I, Robot is less about robots conquering humanity and more about robots following rules that turn out to have ambiguous edges. The desktop’s autonomous swapper does not need three laws, but it does need a clear idea of what it is allowed to do, what it must avoid, and when to stop. Autonomy without constraints is not a feature; it is a hazard.

This entry lists what the desktop would have to provide for autonomous cell swapping to be possible.

2. Mechanical provisions

The rack and the cell must be designed as a robotic task, not a human task:

  • Access volume: enough clearance around each slot for a robot arm or slide mechanism to reach, grip, and withdraw a cell.
  • Common interface: every cell of a given type uses the same mechanical, electrical, thermal, and data mating features.
  • Guide and compliance: chamfers, lead-ins, and floating mounts that tolerate the positioning error of the robot.
  • Latch and lock: a mechanism that secures the cell after insertion and releases it before withdrawal, operable without human fingers.
  • Storage bay: a place to park a spare cell and a removed cell during the swap.

3. Sensing and decision

The rack must know the state of its cells and the state of itself:

  • Cell health telemetry: enough sensors to judge when a cell is degraded or failed.
  • Position sensing: knowledge of where the robot mechanism and the cell are during the swap.
  • Force and torque sensing: the ability to detect unexpected resistance and stop before damage occurs.
  • State machine: a clear sequence of safe states, with checks at each transition.

4. Power, data, and thermal continuity

A swap interrupts the services the cell provides. The desktop must survive that interruption:

  • Power margin: batteries or redundant generation that cover the gap while a power cell is removed.
  • Data redundancy: storage and compute paths that do not depend on the single cell being swapped.
  • Thermal inertia: enough mass and radiator capacity to keep temperatures within limits during the exchange.

5. Software and policy

The most difficult provisions are not mechanical:

  • Swap rules: under what conditions is a swap initiated automatically, and when must ground approve?
  • Inhibition conditions: what spacecraft states prohibit swapping, such as maneuvers, eclipses, or anomalies?
  • Fault response: what happens if a swap fails partway through?
  • Logging and replay: every decision and motion must be recorded so that ground can reconstruct what happened.

6. What this changes

  • Autonomous swapping is not a single mechanism; it is a system requirement touching the rack, the cell, the robot, the software, and the operations policy.
  • Many of these provisions are worth making even for manual or ground-commanded swaps.
  • The next entry will decide whether the desktop should design for this capability.