V7 ARCHITECTURE
A swarm is the output of an industrial civilization.
V7 keeps the civilization, swarm, elevator/tether, R&D, spacecraft and transit models, then adds a representative mission-control layer. It follows named reusable hulls through specific departures, arrivals, tanker flights, failures, repairs and retirement cycles while the aggregate economy continues to represent the enormous fleets required at mature scale.
INTERACTIVE CIVILIZATION MODEL
100-Year Swarm Simulator v7
Bundled orbital snapshot
Live 3D simulation
Explore the current scenario in three dimensions.
● Collectors● Factories● In-transit fleet (where modeled)● Earth / Mars
Drag to orbit · Scroll to zoom · Arrow keys supported
Illustrative geometry: orbital distances use AU; bodies are enlarged and populations are sampled logarithmically. Motion illustrates orbits at the selected year, not elapsed simulation time. Factory and fleet locations are schematic, not calculated trajectories. Counts and power come from this simulation’s results.
MISSION CLOCK
2126
Scrub the century to inspect any modeled year.Solar-system industrial network
Orbital zones, settlements, resource nodes and logistics links at the selected year.
2126 STATE
Power generation, demand and surplus
Delivered photonic power versus Earth + Moon + Mars modeled demand.
Industrial expansion
Collectors and factory nodes
Annual material sources
Earth launch, Moon, asteroid resources and elevator throughput
Technology readiness
R&D-dependent enabling systems
Settlements
Modeled supported population equivalents
Mining + cargo fleet expansion
Fleet-equivalents allocated to extraction and transport
Target cargo arrivals
Material that has completed its return transit and reached industry
Transit pipeline
Dispatched cargo, arrivals and material still between nodes
Propellant economy
Reserve, annual production and flight consumption
Selected-year transfer board
Route state after spacecraft mass-ratio, power, propellant, staging and transit constraints. Kepler propagation is still a simplified two-body model, not a navigation solution.
Model milestones
Derived from this run
Primary constraint
Strongest modeled bottleneck at the selected year
Model note
—
EVENT-DRIVEN MISSION OPERATIONS
Follow the ships, not just the tonnes.
The century model may imply millions of fleet-equivalents, so V7 keeps a capped representative roster of named hulls. Representative hulls now pass through construction queues, accumulate wear and radiation-dose proxies, experience light-time communications and fly on the same selected trajectory model used by the route layer.
Active flight map
Representative vessel positions along selected-year transfers.
2126 OPS
Depot inventory
Modeled split of the shared propellant reserve across operational nodes.
Event log
Departures, arrivals, failures, repairs and retirements in the selected year.
Active mission manifest
Named representative hulls with destination, cargo, cohort scale and transfer progress.
Representative vessel roster
Current hull state, build origin, reuse cycles and next availability.
V7 SOLAR-SYSTEM DIGITAL TWIN
Trajectory, traffic, wear and logistics on one clock.
This layer is deliberately lighter than professional flight dynamics. It can numerically perturb target states and solve zero-revolution Lambert-style transfers, then couples those route estimates to representative spacecraft, dated operations, communications light-time, shipyard queues, depot flow and hardware-health proxies.
3D-ish traffic / trajectory view
Inclination-aware projection of target states and representative active flights. Visual geometry is illustrative; transfer planning uses the numerical state model.
2126 TWIN
Launch calendar
Next modeled favorable geometry with transfer Δv and time of flight.
Traffic + communications
Light-time is physical; relays and autonomy improve availability, not signal speed.
Shipyard construction queue
Representative hulls now require modeled construction time before entering service.
Depot flow ledger
Annualized production, consumption and modeled inventory movement by network node.
SPACECRAFT + DEPOT LEDGER
Every tonne needs a ride.
V7 keeps aggregate mining/cargo capacity for macro throughput while the operations console follows a capped representative set of reusable named vessels, tanker flights and mission events.
DEEP-SPACE TARGET LEDGER
Real bodies, spacecraft-constrained routes.
The body names and orbital elements are reference data. V7 uses a bundled offline element snapshot and can import a user-prepared ephemeris/orbital JSON snapshot. The selected engine can use two-body Kepler propagation or an RK4 Sun+Jupiter perturbation approximation, with optional Lambert-style transfer search. Recoverable reserves, mining economics, spacecraft architecture and trajectory cost remain scenario assumptions—not certified reserves or mission trajectories.
INFRASTRUCTURE LEDGER
Named hubs with real dependencies.
These are project-level scenario assets, not claims that such facilities currently exist. Each hub activates only after its prerequisite thresholds are reached.
RESOURCE LEDGER
Feedstock comes from different resource classes.
V7 counts asteroid feedstock only after scheduled cargo returns arrive; the operations console mirrors representative flights without pretending to enumerate every mature-scale spacecraft. Propellant production can divert part of Earth launch, lunar output and volatile-rich asteroid arrivals away from construction.
INTELLECT COORDINATION LAYER
Allocation changes with the state of the system.
Current resource allocation
Current power allocation
R&D portfolio
DYNAMIC TECHNOLOGY TREE
The path unlocks dependency by dependency.
“Unlocked” means the model’s readiness, year and infrastructure thresholds are met. It does not mean the technology is guaranteed to be feasible in reality.
V7 REFERENCE ROADMAP
Prototype → bootstrap → replicate → expand.
Demonstrate
Autonomous construction, lunar surface power, precision beaming, reusable launch, robotic ISRU and high-reliability orbital servicing.
Bootstrap
Lunar foundries, mass-driver experiments, orbital yards, closed-loop repair and early asteroid prospecting.
Replicate
Distributed factory nodes, NEO prospecting, route-qualified autonomous mining fleets, reusable cargo tugs, propellant depots, mission-control automation, tanker flights, cislunar tether options and mature photonic links.
Move inward
Thermally capable collectors occupy closer solar orbits while main-belt depots, high-Isp cargo transport, refueling and traffic management scale.
Integrate
Planetary relays, industrial settlements, mature multi-target resource routing, persistent event-driven cargo operations, traffic-control automation, shipyard/depot scheduling, reserve power for planetary-engineering research, and a swarm-scale grid.
RESEARCH ANCHORS · CHECKED 2026
Anchor the speculative model in real enabling work.
These sources support the orbital-data interface, trajectory concepts, radiation-reliability assumptions and enabling technology used by the model. V7 deliberately does not embed JPL SSD API calls directly in the site; JPL documentation notes API fair-use/CORS constraints, so the simulator uses bundled data plus explicit file import. They do not imply that industrial asteroid mining, a Dyson swarm, or an Earth space elevator is currently buildable.
NASA/JPL NAIF — SPICE ToolkitProfessional geometry/ephemeris toolkit used as the conceptual benchmark for future higher-fidelity digital-twin work; V7 does not bundle SPICE kernels or claim SPICE-grade propagation.
NASA JSC — Space radiation effectsRadiation hardness assurance considers total ionizing dose, displacement damage and single-event effects. V7 uses only a normalized wear/radiation risk proxy.
NASA NTRS · 2026Modeling Radiation Effects on Spacecraft HardwareCurrent work on event-level radiation effects, including recoverable and destructive spacecraft-hardware events.
NASA/JPL — Horizons APICurrent JPL programmatic ephemeris interface. V7 supports importing a prepared orbital/state-vector snapshot rather than embedding the API in the browser.
NASA/JPL SSD — API documentation & fair useNotes one-request-at-a-time service expectations and that SSD APIs should not be embedded directly in websites under NASA CORS policy.
NASA/JPL — Small-Body Database APIMachine-readable small-body orbital data and the basis for the bundled/importable orbital-element schema.
NASA/JPL SSD — Orbital elements FAQExplains that osculating elements can be used for two-body propagation but grow less accurate away from their epoch; V7 labels that limitation explicitly.
NASA — Solar Electric PropulsionReference for high-Isp Hall-effect electric propulsion and long-duration powered transport.
NASA Science — Psyche SpacecraftReal Hall-thruster reference: solar power falls substantially in the main belt, and thrust is low despite high propellant efficiency.
NASA — Space-Based Solar PowerIdentifies autonomous operations, efficient wireless power beaming, launch economics, and in-space assembly/maintenance as major capability gaps.
NASA TechPort — High Efficiency Laser Power Beaming ReceiversReports that diffraction and low end-to-end efficiency remain central laser power-beaming challenges.
NASA — In-Situ Resource UtilizationNASA is developing ways to obtain water, oxygen, propellants and construction materials from the Moon, Mars and asteroids.
NASA TechPort — ISRU-Based Power on the MoonActive work is maturing autonomous processing of lunar regolith into silicon solar cells, aluminum conductors, oxygen and other products.
NASA TechPort — TYMPODevelops tethered lunar power and communications over long distances; it is adjacent tether technology, not a lunar space elevator.
NASA NTRS — Space Elevator Technology ConceptsHistoric NASA study work highlights ultra-high-strength tether materials and demonstrations as critical Earth-elevator challenges.
NASA Science — Bennu FactsReference for the carbon-rich near-Earth target used in the v4 logistics ledger.
NASA Science — 433 ErosReference for the S-type near-Earth asteroid and its history as the first asteroid orbited and landed on by a spacecraft.
NASA Science — 4 VestaReference for the differentiated main-belt target used in the v4 mineral-route model.
NASA Science — Ceres FactsReference for the water-rich dwarf planet / main-belt resource target.
NASA Science — 16 PsycheReference for the metal-rich main-belt target; NASA notes current estimates of roughly 30–60% metal by volume.