Task 006: Episode 1 Content Analysis

Status: DONE (session 2026-02-23)

Goal

First end-to-end analysis: identify orbital transfer descriptions in Episode 1, extract ΔV claims, and evaluate plausibility.

Depends on

• Task 002 (orbital mechanics library)
• Task 004 (subtitle data)
• Task 005 (report pipeline)

What was done

• Researched Episode 1 source material (sm45280425) and worldbuilding document (note.com/yuepicos)
• Extracted ship specs (Kestrel: 48,000t, 9.8 MN, D-He³ fusion pulse) and contract details (72h deadline)
• Consulted Codex on analysis methodology (brachistochrone model, distance scenarios, framing)
• Extended orbital.ts with Jupiter constants, orbitalPeriod, brachistochrone functions
• Created ep01-analysis.ts with full analysis module (Hohmann baseline, brachistochrone requirements, ship capability, mass sensitivity)
• Created ep01-analysis.test.ts with 29 tests (all passing)
• Created episode report JSON at reports/data/episodes/ep01.json with 4 transfer analyses
• Created session log at reports/logs/2026-02-23-ep01-analysis.md
• Verified end-to-end pipeline: npm run build generates site with Episode 1 report
• All 105 TS tests + 45 Rust tests passing

Key Findings

• Hohmann baseline: 10.15 km/s ΔV, ~1,127 days — far too slow for in-universe setting
• 72h brachistochrone (closest, 3.68 AU): requires ~33 m/s² (3.3g), ~8,497 km/s ΔV
• Ship capability: 0.204 m/s² (0.02g), max ΔV ~52.9 km/s — ~160x gap
• Verdict: Implausible with stated specs, but worldbuilding is internally consistent (72h extreme vs 150h normal)
• Mass ambiguity (48,000t for 42.8m ship) is likely key factor

Follow-up ideas

• Analyze with subtitle data once available (actual dialogue ΔV claims)
• Investigate mass interpretation further
• Add interactive WASM-powered brachistochrone calculator to report