Ring choreography is the cluster-scale coordination that recovers and reuses the rings spent as reaction mass in free-strand propulsion. Each propulsive push leaves its reaction mass drifting, so a transport cluster must continuously capture the loose rings, cancel or bank the momentum they carry, and re-form them into working strands. The orchestrated motion of thousands of rings and strands weaving between co-orbiting habitats is known colloquially as the ballet; the term names an engineering discipline, not an aesthetic one, though the resemblance from a habitat window is the reason it stuck.

The conservation ledger#

A transport cluster is a closed mechanical system to good approximation: absent external forces, its total momentum is conserved, and propulsion only moves momentum among its parts. A free-strand launch transfers momentum from a vehicle to a batch of rings; recovery transfers it onward from the rings to a destination. Nothing is expended — the rings are a working medium, not a consumable — but the books must balance, and ring choreography is the practice of keeping them balanced. Energy is a separate account: it is supplied electrically at terminals and recovered regeneratively, so the choreography conserves momentum while sourcing and sinking energy as needed.

Capture#

Capturing a drifting strand is the time-reverse of launching from one. A receiving strand is extended into the path of the incoming rings and accelerated to match their velocity, after which the relative motion is nulled magnetically over a short corridor. To arrest a typical recoil of 10 m·s⁻¹ at a gentle 0.15 g takes

d = Δv² / 2a ≈ 10² / (2 × 1.5) ≈ 33 m, t ≈ 7 s,

and only a few metres if decelerated at one gravity. Capture is therefore far less demanding than launch — the relative velocities are small and the corridors short — and the binding requirement is not force but timing: the catcher must be in place, matched, and aligned before the rings arrive. Loose individual rings, rather than intact strands, are gathered the same way by a terminal’s collector and re-threaded.

Momentum banking and traffic balancing#

Recovered momentum has three destinations. It can be cancelled against an opposing transfer — an outbound launch in one direction paired with an inbound capture from the other, so the two nearly annul and little reaches the structure. It can be banked in a habitat’s primary structure, a reservoir of order 10⁹–10¹² kg that absorbs the ≈ 3 × 10⁶ kg·m·s⁻¹ of a single launch as a velocity change of only millimetres per second. Or it can be forwarded directly to a destination structure as delivered thrust.

Banking is bounded by how far a structure may be allowed to drift. A hub of 10¹¹ kg subjected to fully one-sided traffic of 10³ launches per day accumulates

Δv ≈ (10³ × 3 × 10⁶) / 10¹¹ ≈ 0.03 m·s⁻¹ per day,

which is trimmed out periodically and vanishes entirely when inbound and outbound traffic are balanced. Scheduling traffic for approximate balance is thus the central optimisation of ring choreography: it keeps the per-structure momentum budget near zero and minimises the residual that must be corrected by other means.

Ring inventory and redistribution#

Between capture and reuse, rings are held as a managed pool. A cluster running 10³ launches per day at ≈ 2000 rings per launch, with a recovery-and-reissue cycle of about an hour, keeps of order

10³ × 2 × 10³ × (1 h / 24 h) ≈ 8 × 10⁴ rings in flight at once,

plus a buffer reserve — on the order of 10⁵ free rings cluster-wide, some 10⁴ tonnes of hardware, small against the millions of tonnes of the habitats they serve. At a terminal, captured rings are recharged to their working current by flux pumps, checked, and re-formed into new strands; rings that fail inspection are cycled out for refurbishment or replacement by the autopoietic industry, which manufactures the lattice in the first place. The pool size, not any single strand, sets how much traffic a cluster can sustain.

Coordination and collision avoidance#

With ~10⁵ independently moving rings sharing a cluster volume of order 10 km across, the mean spacing is a few hundred metres — sparse, but every ring is tracked and its trajectory planned by a distributed control system so that strands, free rings, and vehicles do not intersect. At a 10 m·s⁻¹ drift a ring crosses that spacing in tens of seconds, leaving ample margin to deconflict; the problem is one of scheduling and prediction rather than of reflexes or density.

The dominant failure to design against is a ring leaving the recoverable envelope — un-recaptured reaction mass becomes orbital debris and a hazard to everything in the cluster. This makes recollection reliability, not propulsion performance, the figure of merit for the whole system. A loss of control is comparatively benign: because each ring’s field lives in a persistent superconducting loop, a ring under no active command simply coasts on its trapped current along a predictable ballistic path, still fully magnetic and so recoverable once control is restored. The choreography is built to tolerate such lapses — to predict where an unattended ring will be and to catch it there — rather than to assume they never happen.