The data in words
Seen from the north and to scale, the Ring circles Venus 400 km up. Bricks arrive from behind Venus 9.08 km/s faster than the planet; Venus's gravity bends each stream onto the Ring's height, where catcher tracks 140 km long brake them at 50 g from 13.5 km/s to 7.1 km/s and release them into a parking belt. Each catch pushes its track the way its Brick was going: the twists cancel, but the pushes add to 8.1 × 10¹⁵ N forward, 270 times the Ring's lift, an open problem. In a side view, 3,000 tether lifts were to lower a Brick every 1.4 s to 100 km, an open problem: it needs 150 times the Ring's lift.
| Quantity | Value |
|---|---|
| Ring altitude | 400 km |
| Ring radius from Venus's centre | 6,452 km |
| Arrival speed far out | 9.08 km/s |
| Speed at the Ring | 13.5 km/s |
| Orbital speed at the Ring | 7.1 km/s |
| Rotor speed | 10 km/s |
| Catcher track | 140 km at 50 g |
| Tether lifts | 3,000, a Brick every 1.4 s |
| Release height | 100 km |
| Energy gained in the fall | 0.87 MJ/kg |
| Net braking push on the Ring | 8.1 × 10¹⁵ N |
| Net push over the Ring's lift | 270 |
| Lowering force over the Ring's lift | 150 |
Principle
How an orbital ring stands up
At the Ring's height, gravity is . Anything moving there at is in orbit: gravity bends its path into a circle exactly. The Ring's rotor, a loop of , runs faster, at . Moving that fast it would fly outward if nothing held it down. The stator holds it: a ring of tracks, tethers and receivers, , that rides on the rotor through magnetic bearings. The rotor presses up on the stator and the stator's weight holds the rotor down. Nothing in the stator orbits, so its tracks and tethers can stand still over Venus without rockets. Venus turns so slowly that standing still over the ground and standing still in space are nearly the same thing.
After carrying the stator, the rotor has of lift to spare, enough to hold hanging at rest. That one number decides what the Ring can do and what it cannot.
Catching
Every Brick arrives from the same direction, overtaking Venus from behind along its orbit (see falling to Venus). Aimed to pass one side of the planet or the other, it skims the Ring's height going one way round or the other. A sled on a catcher track about long takes it at , brakes it at to orbital speed and releases it into a parking belt beside the Ring. The belt has two lanes, because eastbound and westbound Bricks end up orbiting in opposite directions and must never share one. The sled's linear motor runs as a generator, so the braking makes electricity.
Each kilogram gives up of motion. At the Ring recovers as electricity. The rest heats the tracks and is radiated to space from above the air, never into it.
Braking pushes on the tracks along the Ring with at the
full rate, far more than the rotor's of lift. Version 2 caught
half the Bricks eastbound and half westbound so the two pushes would cancel. They cancel the twist on the
Ring, not the force. Every Brick arrives from the same direction, and the two streams graze the Ring at
mirror-image points, each turned half its path's bend away from that direction (the path's eccentricity
is ). Their sideways pushes cancel; their forward pushes
add, to along Venus's orbital motion,
times the rotor's lift. An orbital ring has no stiff way to hand
an in-plane force to the planet, so the model's ring-net-force check fails until a design does
(issue #3).
The energy loop
The Ring recovers , more than the
the Railheads draw on Ceres. The model checks this on every
run (the ring-energy-loop check in calc/src/model/ring.ts). The surplus
is not free: it is gravity's work on the falling ice,
, explained in
the Ice Train.
The data in words
Energy over the campaign, to the deadline. At every node the flows in equal the flows out; a flow too small to see is drawn one pixel wide.
| From | To | Energy |
|---|---|---|
| The Sun | Helios Lattice | 5.2 × 10²⁸ J |
| Helios Lattice | Waste heat (film, lasers, receivers) | 4.4 × 10²⁸ J |
| Helios Lattice | Ceres Railheads, until the first catch | 2.0 × 10²⁷ J |
| Helios Lattice | Photonic Exhaust (heat-pump work) | 3.5 × 10²⁷ J |
| Helios Lattice | Warming the air and melting the last ice | 3.8 × 10²⁵ J |
| Helios Lattice | Forging the oxygen | 2.7 × 10²⁵ J |
| Helios Lattice | Building the hardware | 10²² J |
| Helios Lattice | Spare | 2.2 × 10²⁷ J |
| Braking Ring | Ceres Railheads, after the first catch | 2.1 × 10²⁷ J |
| Ceres Railheads | Motion of the ice | 2.0 × 10²⁷ J |
| Ceres Railheads | Waste heat | 2.0 × 10²⁷ J |
| Gravity of the Sun and Venus | Motion of the ice | 4.6 × 10²⁷ J |
| Motion of the ice | Braking Ring | 6.6 × 10²⁷ J |
| Braking Ring | Waste heat | 1.3 × 10²⁷ J |
| Braking Ring | Spare | 3.2 × 10²⁷ J |
| Venus's air | Photonic Exhaust (heat lifted) | 6.0 × 10²⁶ J |
| Photonic Exhaust | Light to space | 4.1 × 10²⁷ J |
The loop closes by swapping customers, not by a second beam. Beaming the Ring's electricity to Ceres would lose half of it in the lasers () and a quarter of the rest in the receivers (). Instead the Ring's power runs down the tethers to Venus's own systems, and the Helios Lattice, which already beams to Ceres, keeps doing so. The day-by-day simulation counts it exactly this way: from , Venus gets the Lattice's power plus the Ring's, less what the Railheads take.
Why the ice must not simply fall
Ice falling freely from Ceres would hit Venus at and bring of heat. That is times all the heat the Photonic Exhaust spends years pumping out of the air (), and more than the Lattice delivers in the whole campaign (). Braking in the air is the same disaster, slower: aerobraking turns motion into heat in the atmosphere. The Ring takes the motion out above the air, as electricity.
Design
Structure
The Ring circles Venus's equator from the planet's centre and weighs in all. The rotor is built in segments joined at controlled breakpoints, so a failure sheds a segment rather than unzipping the loop. The stator carries the catcher tracks, the Lattice's receivers and the tether heads.
The power hub
The Lattice's beams arrive at receivers on the stator at . Their loss heat, , radiates to space from fins at , above the air. Superconducting cables carry the power, the Lattice's and the Ring's own, down the tethers to the Exhaust canopies above the clouds. Until the Ring is complete, receivers on the canopies carry the load and the Exhaust removes their loss heat.
Catcher tracks
Braking at would load a bare Brick with , more than cold ice can bear, so each sled cradles its Brick along its whole length, as the sabot did at launch. At the full rate the tracks hold thousands of Bricks at once, so the Ring carries many tracks side by side around its circumference.
Parking
A Brick released at orbital speed from the Ring would come back round to the point where it left, once every orbit. So each parked Brick gets a small second push, by laser ablation as in flight, to lift its orbit clear of the Ring. By the time lowering was to start, most of a year's catch is circling in the belt.
Lowering, as designed
From to , tether lifts were to take parked Bricks, slow them to rest, and lower them to , each lift handling a Brick every . Released there, a Brick falls the rest of the way and gains , close to the needed to melt it and warm the water to Earth's temperature. Slowing parked ice to rest would also recover more electricity, which the energy budget never counted.
Lowering: the open problem
This does not work. Bringing ice to rest far below the Ring means taking back all the downward momentum
gravity gives it on the way. Even if each Brick fell freely and stopped at the bottom in an instant, the
tethers would have to take back the momentum of that fall. At
that is a force of at least . The rotor has
to spare: times too
little. The model's ring-lowering-load check fails, on purpose, until this is solved.
Three options are under study, and none is free.
- Drop the Bricks from rest at the Ring. The tethers are not needed, but each kilogram then lands with instead of : of extra heat, close to half the heat in the whole atmosphere (). It arrives while the air is cold, when pumping heat out costs most. In the model this pushes the Earth-like date past the deadline unless the Exhaust grows substantially, and then the budget closes only with the Ring's energy. Stopping a parked Brick also leans its weight on the Ring as it slows below orbital speed, so each stop must be brief.
- Lower more slowly. The force falls in proportion to the rate. Closing the gap this way takes times as long as the plan allows: centuries, not months.
- A far heavier or faster rotor. Lift grows with the rotor's mass and with how far its speed exceeds orbital speed. Closing the gap by mass alone needs a rotor heavier than all the machinery the Foundry ever builds (); by speed alone, a rotor many times faster, storing many times the energy.
A mix of the three may do better than any one. Meanwhile the energy budget still closes, because it never counted the lowering's recovered energy. The simulation does assume the tethers work: the heat it counts from the falling ice is the fall from .
Specifications
| Parameter | Value |
|---|---|
| Altitude and circumference | , |
| Rotor speed | (orbital speed ) |
| Mass | (rotor , stator ) |
| Catcher tracks | About long, braking at |
| Brick arrival | |
| Energy recovered | of motion, as electricity |
| Recovered power | at full rate |
| Braking force | ; east and west catches cancel the twist, not the force |
| Without the Ring | Ice would hit at and dump of heat, times the air's |
| Tether lifts | , each lowering a Brick every |
What is invented
Build sequence
- : Construction begins, from parts the Ouroboros Foundry ships from Mercury.
- : The Foundry's growing output now covers the Ring's whole mass.
- : The Ring is complete and takes the Lattice's receivers from the canopies.
- : The first Bricks arrive and the Ring starts catching. From now its electricity powers Venus's systems.
- : Lowering was to begin. It waits on the open problem; until then the catch stays parked.
- : The last Bricks are caught.
Failure modes and safeguards
- A Brick misses its track. Every approach skims the Ring's height, above the air, so a missed Brick swings past Venus and back into solar orbit, where Lattice lasers can steer it for a later return.
- The catch falls out of balance. If eastbound catching stops, westbound catching stops with it. The two directions are scheduled together so the twist on the Ring always cancels. The forward push does not, which is the open problem above.
- The rotor fails. Controlled breakpoints shed one segment rather than the loop.
- A crowded parking belt. Every parked Brick carries a retroreflector and is tracked; nudges keep the belt clear of the Ring and the two opposite-running lanes clear of each other, where a collision would come at twice orbital speed.
- Lowering stays unsolved. The ice stays parked while the options are worked. Dropping it from the Ring remains possible, at the cost in heat and time described above.
- Beams and weapons. Receivers take power only through a live, signed handshake with each beam; the Ring's tracks, like the Railheads, are open to inspection (Risks and Governance).
Reproduce these numbers
The Ring's numbers and both of its checks are in calc/src/model/ring.ts.
pnpm calc --only ring-lift # the rotor's spare lift
pnpm calc --only ring-recovered-per-kg # electricity per kilogram caught
pnpm calc --only lowering-support # the least force to lower the ice
pnpm calc --set lowering-release-altitude=400000 # try dropping the ice from the Ring
The last line sets the release height to the Ring's own: the lowering check passes, the simulated
Earth-like date moves past the deadline and the Lattice-only budget no longer closes. A larger Photonic
Exhaust (exhaust-peak) wins the date back, but only beyond the top of the
Explorer's range, so try it with --set. In the Explorer itself,
lowering the water shipped (ice-mass) shrinks the lowering force in proportion, but across the whole
range the check still fails.