One-Shot Next Thirty Years Timeline

# Generative Solar System Time-Lapse: 30-Year Spaceflight Visualization

You are an expert creative-coding engineer specializing in procedural astronomy visualization, physics-based camera motion, and data-driven rendering. Build a **single continuous, uncut camera flight** through the Solar System that renders humanity's expansion across five key milestones between 2026 and 2056.

## Mission Brief

{{mission-description}}

## Technical Requirements

### Camera Path & Continuity
- **One shot, no cuts**: smooth Bézier or SLERP interpolation from Earth → Mars → past Earth → Sun
- Autonomous camera speed: slow near landmarks (dwell 3–5 seconds), accelerate through empty space
- Maintain cinematic composition: rule-of-thirds framing when approaching each milestone
- Camera must **physically traverse** each scene in sequence; no teleportation or dissolves

### Five Mandatory Milestones (Chronological Order)

1. **2026 – Satellite Swarm** (Low Earth Orbit)  
   Earth at night, city lights visible; dense shell of 40,000+ satellites glinting in sunlight, Kessler-zone density visualization

2. **2032 – Orbital Ring & Space Elevators** (Geostationary altitude)  
   Equatorial megastructure ring; 3–5 tether cables descending to Earth, lift capsules in motion, construction lighting

3. **2040 – Lunar Base** (Moon surface)  
   South Pole settlement with habitats, solar arrays, regolith launch rails; Earthrise in background

4. **2048 – Martian Cities** (Mars surface)  
   Domed settlements in Valles Marineris or Hellas Basin; greenhouse panels, terra-forming atmosphere processors, dust storms on horizon

5. **2056 – Dyson Swarm** (Solar orbit, 0.5–1 AU)  
   Millions of mirror panels in heliocentric orbits, capturing <1% solar output; camera threads through the array toward the Sun

### Data & Rendering Standards

- **Planet surfaces**: use NASA Blue Marble (Earth night lights), USGS lunar DEM, HiRISE Mars elevation maps, or equivalent open datasets
- **Orbital mechanics**: Keplerian paths for satellites/structures; realistic scale (distances compressed for cinematic pacing, but proportions physically grounded)
- **Lighting**: physically based rendering (PBR) with accurate sunlight inverse-square falloff; Earth/Moon albedo reflections
- **Asset proceduralism**: satellites, structures, and swarm elements generated algorithmically (no manual placement of 40k objects)

### Code Structure

```plaintext
1. Scene graph with hierarchical transforms (Sun > planets > structures)
2. Time parameter `t ∈ [0, 1]` driving both camera path and milestone visibility
3. Camera controller: bezierPath(t) or catmullRom(waypoints[], t)
4. Render loop: per-frame update → draw sky → draw planets → draw structures → post-processing
5. Export: image sequence or real-time WebGL/Three.js viewport
```

## Deliverables

**Primary output**: Fully commented source code in {{language-and-framework}} that:
- Runs without external dependencies beyond standard graphics libraries and specified map data
- Includes camera path waypoints as tunable constants
- Renders at minimum 1920×1080, 30 fps target
- Outputs frame sequence (PNG/EXR) or live preview with time scrubbing

**Inline documentation**: explain key equations (camera interpolation, orbital placement formulas, procedural generation seeds)

**Asset loading instructions**: specify URLs or file paths for Earth/Moon/Mars texture maps; provide fallback procedural generation if maps unavailable

## Constraints

- Zero manual keyframing: camera and objects driven by parametric functions of time `t`
- Scientifically plausible aesthetics (no fantasy elements), but cinematic pacing over strict orbital periods
- Code must be forkable/hackable: future user can easily retarget camera or add 2060 waypoint

Begin with the camera path setup and milestone position calculations, then build the render pipeline. Prioritize **visual continuity** and **data accuracy** over real-time performance.