Skip to content

Repository files navigation

StarBound

Explore a civilization powered by a star.

An interactive Dyson swarm laboratory — from Mercury resources to electricity on Earth.

OPEN MISSION CONTROL ↗ · DOWNLOAD THE PITCH DECK · READ THE ARCHITECTURE

CI MIT OpenAI

StarBound — independent solar collectors surrounding the Sun

Generated concept artwork. The application separates its animated concept view, orbital visualization and numerical simulation.

A megastructure is an engineering problem before it is a spectacle. StarBound lets you change the industrial plan, break the thermal budget, lose the power beam, and inspect what survives. GPT-6 Astra proposes a policy; a deterministic engine calculates its consequences.

Try it · 60-second tour · Measured results · Run locally · Documentation

A mission in sixty seconds

Recorded StarBound demo: the animated swarm, zoom controls, receiver resizing and a blocked Earth link

Recorded from the public application. The opening motion is illustrative concept animation; the power figures are calculated by the engine. Watch the MP4 · Narration script

Try this Watch this change
Explore the swarm Collectors animate automatically. Pan, zoom, pause, or switch to Live orbits.
Resize Earth's receiver Set its diameter to 1 km: baseline Earth power falls from 13.23 MW to 3.48 MW.
Lose the transmission path Load Sun blocks Earth transmission: Earth delivery becomes 0 W.
Stop the excavation fleet Safe mode reruns the mission with no excavation; production loses its feedstock.
Break the cooling design At 0.3 AU and radiator ratio 0.5, the model reaches 783 K and disables electrical output.
Apply Astra's proposal Recompute its recorded policy against the same constraints and inspect the result.

Nine tabs cover mission control, robots, manufacturing, collectors, Earth power, civilization, Astra, construction and research. The power readout stays visible across them. Complete control guide

From Mercury to Earth

flowchart LR
  Seed[Imported robots<br/>and industrial seed] --> Mine[Mercury excavation]
  Mine --> Refine[Refining]
  Refine --> Build[Collector manufacturing]
  Build --> Launch[Launch and insertion]
  Launch --> Swarm[Solar swarm]
  Swarm -->|Reinvested power| Build
  Swarm --> Optical[Optical orbital relay]
  Optical --> Ground[Microwave downlink<br/>and Earth grid]
  Swarm -.-> Future[Separate space-use<br/>and dense-swarm estimates]
  classDef solar fill:#312416,stroke:#c6a16b,color:#fff2d4;
  classDef earth fill:#142836,stroke:#73a7c4,color:#d8f2ff;
  class Swarm solar;
  class Optical,Ground earth;
Loading

This is a proposed engineering sequence. The monthly model constrains industrial throughput, mass, energy and power delivery. Landing, detailed launcher sizing and near-total-capture estimates are separate calculators. Twelve-stage process · Equations and assumptions

Astra proposes. The engine measures.

The challenge: deliver at least 10 MW at month 120 while minimizing mined Mercury ore. The endpoint power already includes an assumed 75% link availability. Astra may change five policy fields; it cannot change the fixed budgets, physical constants or scoring rules.

Method Evaluations Best mined ore Endpoint Earth power Recorded time
GPT-6 Astra 3 proposals 0.128494 Mt 13.233 MW 162 s
GPT-5.6 Sol 3 proposals 0.128494 Mt 13.233 MW 249 s
Conventional grid search 1,008 simulations 0.128494 Mt 13.233 MW 0.5 s

The mining scores tied. One experiment per model does not establish general superiority or a latency benchmark. Search had a different evaluation budget. The recorded policies reduce mining from the ten-year baseline's 3.92 Mt while preserving its endpoint delivered power under the fixed receiving assumptions.

The public site includes the real recorded experiments. Live model inference runs through the included local adapter using your own Codex login.

Protocol · Astra record · Sol record · Search record · Comparison JSON

One numerical authority

flowchart TB
  Controls[Mission controls] --> Engine[Deterministic monthly engine]
  Engine --> Results[Telemetry, ledger and exports]
  Diagnostics[Separate engineering calculators] --> Bounds[Landing, launch and space-use bounds]
  subgraph Local experiment
    Astra[GPT-6 Astra] --> Proposal[Structured proposal]
    Proposal --> Validate[Allowed-field validation]
    Validate --> Engine
    Engine --> Grade[Independent grade]
    Grade -->|Measured feedback| Astra
  end
  Grade --> Record[Published JSON records]
  Record --> Replay[Public experiment replay]
  classDef core fill:#18272e,stroke:#7aabb8,color:#edf8ff;
  class Engine,Validate,Grade core;
Loading

The same TypeScript engine runs in the browser and in Node experiments. It tracks monthly material residuals, production energy, thermal limits, Gaussian-beam capture and receiver caps. React and Three.js render the console; the model supplies proposals and explanations, not physical metrics or grades.

Detailed architecture and execution plan · 20 numerical tests · Validation · Claim audit

Run locally

Requires Node.js 24+.

git clone https://github.com/vnmoorthy/starbound.git
cd starbound
npm ci
npm run dev -- --hostname 127.0.0.1 --port 3000

Open http://127.0.0.1:3000. The simulator and recorded experiments work without a model account.

Run a live Astra experiment
npx codex login status       # If needed: npx codex login
npm run lab

Open the temporary local URL printed by the adapter. It binds to loopback, requires a per-process token, and accepts one run at a time. Keep the token private. Inference consumes your own model quota; the public website does not receive your login credentials.

npm run experiment:astra
npm run experiment:sol
node scripts/summarize-results.mjs

Full setup and comparison protocol

Validate or reproduce the numerical results
npm run typecheck
npm run lint
npm test
npm run build
npm run simulate
npm run experiment:search

CI runs types, lint, numerical tests and production compilation. Ordinary validation does not call a model. The experimental records retain engine v1.0; the current v1.1 defaults reproduce their baseline behavior.

What the power could do

Baseline year-30 Earth delivery is approximately 13.23 MW, or 0.116 TWh/year. Illustrative alternatives are 29 million m³ of desalinated water, 2,109 tonnes of hydrogen, 29,000 household-years of electricity, or a 13.23 MW computing-facility load.

Each uses the entire same electricity budget. These are energy equivalents, not demonstrated plants or solved global problems. Conversion assumptions

Read deeper

If you want to… Start here
Understand every control Console guide
Review the engineering Physics · Research register
Extend the application Architecture · Contributing
Reproduce the AI experiment Astra protocol · Recorded evidence
Present the project PowerPoint · Demo script
Challenge a claim Claim audit · Report a scientific issue

Scope and next steps

StarBound is a reduced-order engineering model, not a validated construction plan. The seed infrastructure and Earth relay are assumed endowments. Extraction chemistry, robot navigation, manufacturing readiness, collision avoidance, station keeping, relay cooling and lifecycle economics are not validated. Monthly growth stops at 1% projected coverage; near-total-capture estimates use separate bounds.

Next: explicit inventories and factory delays, time-dependent trajectories and beam networks, uncertainty analysis, and a harder repeated Astra/Sol evaluation with held-out failures. Execution plan

Built by vnmoorthy with AI assistance at the GPT-6 Astra Hackathon SF, September 8, 2026. MIT license · Third-party notices. No affiliation or endorsement by SpaceX, NASA, OpenAI or the cited researchers is implied.

About

Explore a civilization powered by a star. An interactive Dyson swarm laboratory with Mercury industry, Earth power delivery and Astra experiments.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages