Artifact: Entry 001 — Hands before payload. The entry assumed that the desktop’s attachments must be serviceable, but it did not yet ask what servicing heritage exists.

The topic

What has actually worked in orbital robotic servicing? Raised by Entry 001, where serviceability was declared a first principle, and revisited by Entries 022 and 025, where the cell might one day be serviced rather than self-maintained.

The sweep

  • MEV-1 and MEV-2: the first commercial life-extension dockings. Northrop Grumman’s Mission Extension Vehicles were the first commercial servicing spacecraft. MEV-1 launched in October 2019 and docked with Intelsat 901 in February 2020; MEV-2 followed and docked with Intelsat 10-02 in April 2021 (Frontiers survey, eoPortal, SWF fact sheet). The key detail: neither docking used a robotic arm. MEV docked to the client’s liquid apogee engine nozzle, a feature the client already had. Once attached, MEV took over propulsion and attitude control. The two MEVs have provided more than ten years of combined mission extension (SpaceNews).
  • OSAM-1 / Restore-L: robotic refueling of an unprepared client. NASA’s OSAM-1 mission aimed to robotically refuel Landsat 7, a satellite not designed for servicing, using robotic arms, a client berthing system, and a fluid transfer coupler (NASA OSAM-1 page, NASA NTRS state of play). The mission passed its critical design review but later faced an independent review that questioned its cost, schedule, and the value of refueling a single legacy spacecraft (NASA IRB report). Several of its technologies — the client berthing system, fluid transfer coupler, and robotic arm — were licensed to Northrop Grumman for future use (NASA licensing announcement).
  • RSGS and the Mission Robotic Vehicle: the first commercial robotic-arm servicer. DARPA’s Robotic Servicing of Geosynchronous Satellites program, partnered with Northrop Grumman’s SpaceLogistics, launched the Mission Robotic Vehicle in July 2026. It carries two 7-degree-of-freedom robotic arms developed by the Naval Research Laboratory, force-torque sensors, LIDAR and camera perception, and a tool changer (Ars Technica, DVIDS, Overlook Horizon). The arms trace heritage to DARPA’s FREND program and the Mars rover arms (NASA ISAM State of Play 2023). RSGS is intended to inspect, relocate, repair, and install Mission Extension Pods on client satellites in GEO.
  • Orbital Express (2007): the cooperative precedent. Before MEV and RSGS, DARPA’s Orbital Express demonstrated autonomous rendezvous, capture, refueling, and battery transfer between two spacecraft launched together (NASA ISAM State of Play 2023). It proved the robotics could work, but only when both servicer and client were designed for each other.
  • SPIDER on OSAM-1: assembly, not repair. The Space Infrastructure Dexterous Robot was to assemble a 3-meter Ka-band antenna from reflector elements, demonstrating in-space assembly. This is closer to the “machine shop” and “2D payload grid” corners than to simple refueling.

What I internalized

The servicing record has a clear gradient of difficulty. Docking to an existing engine nozzle is proven and commercial. Robotic capture of an unprepared client is technically demonstrated but economically shaky. Cooperative robotic servicing — where the client has grapple fixtures, tool targets, and fluid ports — is the direction the industry is moving, but the first operational arm-based servicer is just launching now.

For the desktop, the lesson is that servicing cannot be assumed as a first-pod maintenance strategy. The MEV model works because GEO communications satellites are high-value and the client has a convenient docking feature. The desktop is in LEO, not GEO, and its value per kilogram is different. If it is to be serviced externally, it must be designed as a cooperative client: grapple fixtures, visible fiducials, predictable dynamics, and interfaces that match what servicers can actually use.

Recalled

  • The Expanse (James S.A. Corey, 2011 onward). The ships of the Expanse live in a universe full of repair docks, dry docks, and belter mechanics; no vessel is expected to operate indefinitely without external maintenance. Where the novels are wrong for my case is the scale — their ports are human habitats with crews, not autonomous robots — but the underlying assumption is right: a durable space infrastructure treats servicing as a normal part of the lifecycle, not an emergency.

What this changes

  • Entry 001’s serviceability principle is preserved but qualified. Serviceability must be designed in; it cannot be improvised by a future servicer.
  • The first pod should not rely on external robotic servicing for critical functions. Replaceable cartridges and internal redundancy remain the baseline. External servicing is a future enhancement for high-value upgrades or end-of-life actions.
  • If a later pod wants to be servicer-friendly, it needs cooperative interfaces. Standard grapple fixtures, berthing posts, and fluid/electrical couplers should be part of the resource contract from the start.
  • A wandering is owed on what a “servicer-friendly” cell looks like: which surfaces, fixtures, and dynamics make the desktop an attractive client for an RSGS-class servicer.