Once a spacecraft can generate power, reject heat, and accept robotic replacement units, its central tower no longer needs to end with the equipment it carried at launch. It can become the first segment of an orbital rack.

The interactive model extends the shielded power–compute cell along its anti-Sun axis. Add or remove rack bays, select a compute, storage, radio, or camera cartridge, and move the service control to watch Hexadrone extract it sideways without separating the equipment below.

The architectural rule

Extend the permanent rack axially; replace functional equipment laterally.

A literal chain of equipment blocks appears simple until an interior block fails. Removing that block would leave everything below it structurally unsupported and would break every power and data connection passing through it.

The rack therefore separates two kinds of hardware:

Long-lived infrastructure Replaceable equipment
Axial structural rails Compute cassette
Repeating bay frames Storage and network cartridge
Redundant power trunks Radio cartridge
Redundant data trunks Camera or navigation cartridge
Timing, grounding, and safing Battery or power-conditioning cartridge
Cold rails and radiator connection Future payload cartridge
Hexadrone docking features End-of-life or upgraded hardware

The rails remain continuous when a cartridge leaves. Downstream bays retain structure, power, data, and thermal service.

Sunward and anti-Sunward

Top and bottom have no invariant meaning in orbit. This architecture has a more useful directional vocabulary:

Sunward
   │
transparent particle shield
hard-tile photovoltaic plane
deployment head and permanent service spine
thermal parasol around the service axis
   │
compute bay
storage / network bay
radio bay
camera or terminal payload bay
   │
anti-Sun extension port

The Sunward head owns generation and protection. The anti-Sun side provides radiator view, robotic approach, sensor placement, and the interface for another rack segment.

A standard rack unit

All rack segments share one square or chamfered-square cross-section. Their axial height is measured in integer multiples of a future rack unit—1U, 2U, 3U, and so on.

The actual dimension of one unit is deliberately not fixed yet. It should follow:

  • Hexadrone payload, reach, and extraction-force capability;
  • practical compute and radio cartridge dimensions;
  • launch-stack height and fairing utilization;
  • structural mode and attitude-control limits;
  • connector and cold-plate geometry.

Each permanent segment repeats the same interface bands: structural corners, cartridge guides, redundant buses, dry thermal contact, service fiducials, and an anti-Sun extension collar.

What travels through the rack

The rack is more than a mechanical stack.

Redundant power

Two isolated power trunks pass through every permanent segment. Each bay taps them through protected switches. A shorted cartridge can be disconnected without opening power continuity to the rest of the stack.

Redundant data

Two independent data paths also continue through the bay frames. A cartridge joins as an endpoint or switched participant; it is never the irreplaceable repeater required to reach the equipment below.

Time, ground, and safing

Hardwired service-state, emergency-stop, cartridge-presence, latch-state, timing, and grounding paths remain available even when a cartridge is absent or its software has failed.

Heat

Each cartridge clamps against a permanent cold rail using a dry, preloaded thermal interface. Heat pipes or fluid circuits remain on the long-life side of the service boundary. Routine replacement does not open a coolant connection.

The resource contract

Matching geometry is not enough to make two modules compatible. Every cartridge needs a machine-readable resource contract:

Domain Declared properties
Power average, peak, startup, safe-mode, and ride-through demand
Thermal rejected heat, temperature range, interface resistance, and transient capacity
Data bandwidth, latency, timing, trust domain, and redundancy
Dynamics mass, centre of mass, inertia, and permitted rack position
Environment field of view, antenna clearance, contamination, plume, and electromagnetic constraints
Service grapple point, extraction envelope, handling moment, and retained-hardware destination

Before accepting a new segment or cartridge, the stack controller evaluates the resulting configuration. A shape may fit perfectly and still be rejected because it blocks a camera, detunes an antenna, exceeds radiator capacity, lowers the first bending mode, or leaves Hexadrone without an extraction corridor.

Stackable does not mean order-independent

Compute and storage usually tolerate an interior position. Cameras, antennas, radiators, and propulsion do not.

  • A camera may need the terminal anti-Sun bay for a clear field of view.
  • A radio needs antenna keep-out volume and electromagnetic separation from other transmitters.
  • A thermal augmentation module needs a cold-space view.
  • A thruster module needs a plume corridor that cannot intersect PV tiles, shields, sensors, or a servicing drone.
  • A heavy battery placed far down the rack may exceed bending or attitude limits even when electrical capacity is available.

The stack is therefore configured, not merely piled.

Adding another block

Hexadrone can extend the rack without rebuilding the deployment head:

  1. The stack controller validates the proposed segment and payload manifest.
  2. Hexadrone captures the restrained empty segment from a carrier.
  3. It braces against the existing terminal frame.
  4. Coarse guides acquire the anti-Sun extension interface.
  5. Captive structural latches close and preload.
  6. Ground, identity, orientation, and redundant pass-through buses are tested.
  7. Hexadrone installs the functional cartridge from the side.
  8. The controller updates its structural and resource model.

The terminal end cap is retained and parked. Nothing is released as debris.

Replacing an interior cartridge

Replacement does not require removing the equipment below:

  1. Workload or payload activity stops.
  2. The bay isolates and discharges its power connection.
  3. Hexadrone docks locally and captures the cartridge.
  4. Captive latches release thermal and mechanical preload.
  5. The cartridge translates sideways out of the permanent rails.
  6. Hexadrone secures the removed unit.
  7. The empty bay is inspected.
  8. A replacement is inserted, latched, tested, and energized.

The rest of the rack remains structurally continuous throughout the operation.

One power head, bounded growth

The first maximum-eclipse ledger rejects the original 3 m power claim and provisionally selects a 4 × 4 m power envelope made from four 2 × 2 m structural quadrants. The downstream physical trade resolves that envelope into 60 identical 499 mm tiles on an 8 × 8 bay grid with the centered 2 × 2 bays empty. A complete CFRP/aluminum-honeycomb article allocates 1.444 kg per tile and 86.64 kg for all 60 tiles. The matching front-mounted/rear-serviced receiver adds 1.5125 kg per bay and a 220 mm service aperture, bringing tiles plus receivers to 177.39 kg before the quadrant truss or deployment hardware. One shared 18.0 kg center-well polar presenter now supplies the Sunward handoff: four passive edge clamps retain the tile until the rear Hexadrone captures through that aperture. With current silicon-HJT and five-year degradation allocations, the field provides 2.712 kW at EOL with one physical tile isolated and sustains the 1.519 kW nominal compute-and-housekeeping domain with 35.38% worst-orbit energy margin. Additional camera, radio, storage, or networking loads consume that margin unless compute is derated or another power and thermal module is added.

The rack is geometrically extensible, not physically infinite. Every added segment changes:

  • power and heat balance;
  • first bending and torsional modes;
  • attitude-control authority and settling time;
  • mass properties and disturbance torque;
  • radiator view factors;
  • data and bus losses;
  • service travel and collision corridors.

When one limit is reached, growth moves to another deployment head or to a larger truss connecting several complete stacks.

Why this is a cargo architecture

At launch, the pieces remain ordinary rectangular cassettes that can be arranged in a circular fairing. On orbit, the same interfaces turn them into infrastructure:

  • the deployment head supplies power and heat rejection;
  • permanent rack segments establish structure and resource trunks;
  • cartridges provide replaceable function;
  • Hexadrone performs assembly, upgrade, and repair;
  • empty and failed hardware remains captured in the logistics system.

The spacecraft is no longer defined by the exact payload it carried on launch day. It is defined by the interfaces through which later payloads can join.

Model boundary

The viewer shows geometry, service direction, resource paths, and modular growth schematically. It does not yet select rack dimensions, rail sections, connector families, latch preload, bus voltage, cold-rail material, cartridge mass, structural frequency, antenna geometry, or Hexadrone propulsion and manipulation capability.

Those values will determine how long the stack can become. The architectural invariant comes first: no replaceable cartridge is required to hold the downstream stack together.