Technologies · Everywhere

Choir

Choir runs a trillion machines on three worlds as one system. It is a four-tier autonomous control system that plans around light delays of up to , and its safety core sets hard limits that no machine, and no single person, can override: a Mass Ledger, signed build orders, a kill code, a dead-man switch and a formally verified replication controller. It goes live when the seed foundry lands on Mercury on .

Every number is marked:Physics: Measured, or established physicsPrecedent: Demonstrated in the real world, citedInvented: A breakthrough the plan assumesDesign choice: A size, count or date the plan choosesSelect any number to see how it is computed.

The Phosphoros technology stackThirteen inventions in the place each works, from Earth to Mercury, Ceres, near Venus and Venus, with the flows between them. Each box links to its technology page.EarthMercuryNear VenusVenusCeresseedbuildspartslaser powericefirst factoriesshadeshieldicepowerheatto spaceSeed foundry: launches from Earth in October 2028Seed foundryOctober 2028The first Ceres factories: the only other hardware that leaves EarthFirst factoriesfor CeresOuroboros Foundry: Self-copying industry on Mercury. Online January 2029.Ouroboros FoundryOnline January 2029Helios Lattice: Harvest sunlight near Mercury and beam it. Online June 2033.Helios LatticeOnline June 2033Hesperus Veil: Sunshade, thermostat and day clock. Online June 2032.Hesperus VeilOnline June 2032Thermal Chimneys: Lift deep heat to the cloud tops. Online January 2033.Thermal ChimneysOnline January 2033Photonic Exhaust: Throw heat into space as light. Online January 2033.Photonic ExhaustOnline January 2033Cryo-continents: Store all the CO₂. Online January 2034.Cryo-continentsOnline January 2034Graphite Forges: Split CO₂ into oxygen and carbon. Online January 2035.Graphite ForgesOnline January 2035Ceres Ice Train: Ship the water. Online June 2033.Ceres Ice TrainOnline June 2033Braking Ring: Catch the ice without heating Venus. Online August 2034.Braking RingOnline August 2034Acid Sweep: Remove the sulfuric-acid clouds. Online January 2034.Acid SweepOnline January 2034Aegis Shield: Stop the solar wind stripping the new water. Online June 2034.Aegis ShieldOnline June 2034Genesis Biota: Start an ecosystem. Online September 2036.Genesis BiotaOnline September 2036Choir: Run a trillion machines as one system. Online January 2029.ChoirRun a trillion machines as one system, on every world. Online January 2029.MaterialPowerShade, shield and heatDates: when each leaves Earth or comes online. Click a box for its page.
The technology stack. The seed foundry and the first Ceres factories leave Earth; the Foundry builds everything else on Mercury, the Lattice's beams power it, and the Choir runs every machine as one system. Each box opens its technology page.View sourceSVG
The data in words

Only the seed foundry (launching October 2028) and the first Ceres factories leave Earth. On Mercury the Ouroboros Foundry builds the Helios Lattice and sends parts to the Veil, the Aegis Shield and the Braking Ring near Venus. The Lattice beams power to the Ceres Ice Train and to Venus. Ice goes from Ceres to the Ring and down to Venus, with the Ring's power. The Veil shades Venus, the Aegis shields it, and the Chimneys lift heat to the Exhaust, which sends it to space. The Choir runs every machine.

InventionWhereJobOnline
Ouroboros FoundryMercurySelf-copying industry on MercuryJanuary 2029
Helios LatticeMercuryHarvest sunlight near Mercury and beam itJune 2033
Hesperus VeilNear VenusSunshade, thermostat and day clockJune 2032
Thermal ChimneysVenusLift deep heat to the cloud topsJanuary 2033
Photonic ExhaustVenusThrow heat into space as lightJanuary 2033
Cryo-continentsVenusStore all the CO₂January 2034
Graphite ForgesVenusSplit CO₂ into oxygen and carbonJanuary 2035
Ceres Ice TrainCeresShip the waterJune 2033
Braking RingNear VenusCatch the ice without heating VenusAugust 2034
Acid SweepVenusRemove the sulfuric-acid cloudsJanuary 2034
Aegis ShieldNear VenusStop the solar wind stripping the new waterJune 2034
Genesis BiotaVenusStart an ecosystemSeptember 2036
ChoirEverywhereRun a trillion machines as one systemJanuary 2029

Principle

Light delay decides the architecture

Signals cross the Solar System at the speed of light, and the plan spans much of the inner Solar System. Mercury is to from Venus. Venus is to from Ceres, and Earth is up to from Ceres. Even the Veil is from Venus. A question and its answer take twice as long.

Nobody on Earth can steer a coilgun on Ceres, a sled on the Ring or a slat on the Veil as it happens. So each decision is made at the lowest level that can see enough to make it and act fast enough to matter.

Four tiers

TierScopeDecidesReacts in
CellOne machineIts own actionsMilliseconds
GuildAbout 10,000 machinesTasks and repairsSeconds
WorksOne siteProduction schedulesMinutes
CouncilAll worlds, with human oversightCampaign plans and mass budgetsHours to days

A Cell is one machine deciding its own motion in milliseconds. A Guild of about ten thousand machines shares out tasks and repairs in seconds. A Works runs one site's production in minutes. The Council, with human oversight, sets campaign plans and mass budgets over hours to days. Higher tiers set goals and limits; lower tiers choose how to meet them. A tier that loses contact with the one above keeps working inside its last limits.

Limits that are not up for negotiation

A self-copying industry is the most powerful machine in the plan and the most dangerous. Ouroboros grows from to in doublings, and one unplanned doubling more would double everything. So the rules about replication are not left to software that learns or plans. They live in a safety core that every replicating machine carries, enforced in hardware and proved by mathematics.

Design

The Mass Ledger

The Ledger is an append-only record of every kilogram mined, built, shipped and recycled, copied at every site. Each entry carries a digest of the entry before it, so history cannot be edited without breaking the chain. The Council sets mass budgets, for the Foundry over the whole campaign, and a machine refuses any order that would take its site past its budget.

Signed build orders

Any order to build a machine that can build machines carries a threshold signature: several independent keys must sign it together. Machines check the signature in hardware, so an unsigned or wrongly signed order is refused before any software sees it. Blueprints are checksummed every generation, so copying errors cannot pile up.

The kill code

The kill code is a key split among ten holders on an international board; any seven together can halt all replication, everywhere, within one light delay. No nation, company or person holds enough of it alone. It stops copying, not the planet's life support: the Veil, the cryo-continent refrigeration and the Exhaust keep running.

The dead-man switch

Every replicator needs a heartbeat from the Ledger. After without one it stops building. That is longer than any light delay or routine outage, and a small fraction of one doubling, so a site that is cut off cannot grow far.

The verified replication controller

The part of each replicator that decides whether to build another is small and formally verified: proved mathematically to obey the Ledger, the signatures, the kill code and the dead-man switch, whatever the rest of the machine's software does. Everything clever (planning, learning, optimizing) runs outside it and can only ask.

The digital twin

At the Council tier, a digital twin of Venus and of every machine forecasts phase changes weeks ahead, such as the Clear Rain of and the freezing of the CO₂ seas from . The Works then move canopies, Forges and crawlers before conditions change rather than after.

What it coordinates

  • On Mercury: the Ouroboros Foundry's twelve machine types and the Helios Lattice's Petals. A beam fires only while its receiver answers with a live, signed handshake, and defocuses the moment the handshake drops.
  • Near Venus: the Hesperus Veil's slats, each holding station by itself, and the Braking Ring's catches.
  • Between Ceres and Venus: a Brick is in flight for , so every catch is scheduled when it is launched. Eastbound and westbound catches must balance, so a Railhead that stops on Ceres is matched by a change of plan at the Ring, across up to of delay.
  • On Venus: chimneys, canopies, crawler-rafts, Forges, rock mills and, at the end, the seeding drones of Genesis.

Specifications

ParameterValue
Light delayMercury to Venus to ; Venus to Ceres to ; Earth to Ceres up to
Veil to Venus

What is invented

Build sequence

  • : Choir-sim must run a robot factory unattended, with almost no human help. Pass and kill marks are on the Research Agenda.
  • : Choir goes live with the seed foundry on Mercury. The Ledger's first entry is the seed itself.
  • : The first Lattice Petals fly and Veil slat production begins. Beam handshakes start.
  • : The Veil closes. Choir holds its slats on station and sets its transmission.
  • : The Foundry reaches full scale and its budget; replication stops there. The first Bricks leave Ceres.
  • : The first catch. Ceres and Venus now work as one schedule.
  • : The deadline. Choir stays on: the Veil remains the planet's thermostat, and the cryo-continents need refrigeration for good.

Failure modes and safeguards

  • Runaway replication. The Ledger's budgets, signed build orders and the kill code, each enough alone to stop it (Risks and Governance).
  • A site goes dark. It keeps working inside its last limits, and its replicators stop after without a heartbeat.
  • Copying errors. Blueprints are checksummed every generation; a machine built from a corrupted blueprint fails its first signature check.
  • A stolen key. One key is never enough. Signatures need several, the kill code needs seven of ten, and the board can replace a compromised key.
  • A false alarm. The kill code halts replication only, so using it costs time, not the planet.
  • The twin is wrong. Its forecasts are checked against measurements every day, and the Works keep margins wide enough to absorb a missed forecast.

Reproduce these numbers

Choir's own numbers are the light delays, computed in calc/src/model/outcome.ts; the Veil's is in calc/src/model/veil.ts.

pnpm calc --only delay-earth-ceres-max     # the longest delay the Council plans around
pnpm calc --only delay-venus-ceres-max     # Venus to Ceres at its farthest
pnpm calc --only veil-light-delay          # the Veil to Venus

The delays depend only on the orbits and the speed of light, so no slider moves them. What the Choir must manage scales with the Foundry: in the Explorer, a faster doubling (foundry-doubling-days) brings more machines sooner and leaves less time to audit each generation; a slower one pushes the Lattice, the Ice Train and the Earth-like date later.