R&D CapabilitiesLive now

Stellar Evolution Studio

The System Builder lets you author a star system’s evolutionary fate — converting stars to objects, deciding the outcome of affected planets, and running full gravitational integration until the new configuration stabilizes. Conversions and planet fates follow simplified, built-in stellar-evolution rules.

Go deeper

Public reference. This page explains what Cosmos Genesis does and the science it's based on. Implementation details, such as exact algorithms, tuning values and infrastructure, are kept in our internal documentation.

Design Tools

Phenomena Palette

The System Builder’s Phenomena palette lets you place large-scale astrophysical structures directly into a designed system: Nebula, , , and Dust Cloud.

Placing a Planetary Nebula or Supernova Remnant starts a guided conversion of its host star, walking you through what happens to the planets around it. Nebula and Dust Cloud placements are sized, typed scene objects.

Every phenomenon type reflects a real astrophysical state — are the ionized shells of post- stars, and are the expanding ejecta shells left by or thermonuclear events. In the builder, placing one prompts you to decide what it means for the host star and its planets.

Outputs & Accuracy

Available typesNebula, Planetary Nebula, SNR, Dust Cloud
Trigger scopePlanetary Nebula and SNR start a guided host-star conversion
Nebula / Dust CloudPlaced as sized scene objects with a selectable type

Stellar Conversion

Stellar Remnant Conversion & Planet Fates

When a Planetary Nebula is added to a system, the builder offers to convert the hosting star to a White Dwarf. Surviving planets’ orbits expand to reflect the star’s mass loss, and for each planet swallowed by the star’s giant phase the designer chooses one of three outcomes: remove the planet entirely, turn it into a white dwarf debris disk, or leave it in its current orbit.

The debris disk outcome is motivated by the white dwarf pollution scenario — rocky bodies tidally disrupted inside the of a white dwarf are the leading explanation for the dusty disks seen around some white dwarfs.1 Choosing it replaces the planet with a debris ring at its former orbit; the builder does not simulate the disruption itself.

Adding a core-collapse Supernova Remnant opens conversion to Neutron Star or Black Hole, with a per-planet fate decision: vaporize, eject, or keep. Sudden mass loss can unbind planetary orbits, so the builder suggests a fate for each planet from its orbital distance — close-in planets vaporized, farther ones ejected — and you can accept it or keep the planet. The suggestion is a simple distance rule, not an orbit-by-orbit calculation.

Outputs & Accuracy

PN conversionHost star → White Dwarf
SNR conversionHost star → Neutron Star or Black Hole (core-collapse)
Planet fates (WD)Remove / debris disk / keep — for planets the giant phase swallows
Planet fates (neutron star / black hole)Vaporize / eject / keep
Debris disk contextDusty white dwarf disks — Jura (2003)1
Suggested fateFrom orbital distance — a design aid, not an orbit calculation
ScopePlanets; moons, asteroids, comets follow in future phases

Orbital Mechanics

Keplerian & Many-Body Dual Integration

Every designed system runs in one of two integration modes. Keplerian mode computes clean elliptical orbits from classical orbital elements — , , inclination, and the remaining Keplerian parameters — and is the default for authored systems. Orbits are displayed as ellipses and update when any parameter changes.

mode replaces computed orbits with full gravitational integration. Each body carries a state vector — position (x, y, z) and velocity (vx, vy, vz) in the system’s reference frame — which the integrator advances at each step using contributions from every other massive body. Initial state vectors can be assigned directly in the builder, giving precise control over the starting configuration before integration begins.

Once N-body is running, the system monitors total-energy drift and escaping bodies and grades the configuration stable, marginal, or unstable. After an initial measuring period the Lock Orbits control becomes available — offered as a forced lock if the system has not settled. Selecting it reads the current N-body state, fits Keplerian orbital elements for each body relative to its parent, and writes those back as the system’s Keplerian parameters. Switching to Keplerian mode then shows the new orbit lines in place of the pre-relaxation values.

Outputs & Accuracy

Keplerian modeClassical orbital elements — analytic
N-body modeFull gravitational integration with state vectors
State vector inputsx, y, z, vx, vy, vz per body — user-editable
Stability monitoringContinuous — energy drift and escaping bodies
Lock OrbitsFits Keplerian elements to the current N-body state
Accuracy guardWarns when the timescale is too coarse for the fastest orbit

Generation Pipeline

Galaxy-Scale N-body Connection

Galaxy generation includes an optional step. How it relates to the System Builder’s N-body mode is explained once, on the physics page.

Planned: exporting a designed system — with planet fates decided and orbits locked to the post-relaxation Keplerian parameters — together with its full position and velocity data.

Outputs & Accuracy

ExportPlanned: position and velocity data for designed systems

Roadmap — Coming phases

The following capabilities are in development and are not yet available:

  • ○Nova and Supernova quick-add events in the System Builder — trigger transient energy release directly in the scene
  • ○Extended fate decisions for moons, asteroids, and comets following the same per-body model as planets
  • ○Live remnant conversion for active systems mid-simulation — not just at design time

References

Physics models draw on published literature.

  1. 1.Jura (2003) — White dwarf debris disks from tidally disrupted rocky bodies — Astrophysical Journal Letters 584:L91 ↩