Overview
Apogee Launch Co. — 24-Month Earth-to-Space Program Plan
Planning artifact (fictional). "Apogee Launch Co." is an invented company.
Nothing here builds, tests, or flies a rocket. This deliverable is a complete,
day-by-day plan for a 5-person, $200M, 24-month program whose goal is a
first suborbital flight across the Kármán line (100 km).
What this is
A founding-to-flight program plan answering the request: *"build a rocket ship company from scratch — 5 employees, $200M, 24 months, first rocket from Earth to space; plan every single day."* It ships as:
- An interactive website (
public/index.html) — open it in any browser. It
contains the phase roadmap, a budget burn chart, the crew, milestones, a risk register, and a day-by-day planner covering all 730 days.
- A canonical plan model (
src/plan.mjs) — the single source of truth. - A verification suite (
verify.mjs) — proves the plan is consistent,
complete, and deterministic.
- A proof package (
proof/) — IRS_AUDITOR evidence, limitations, and the
Proof Layer's authoritative decision.
Scope decision (disclosed)
"To space" = crossing the Kármán line (100 km) on a suborbital trajectory. Orbital flight is out of scope at this budget/headcount. The 24-month schedule is disclosed as the program's top risk, not a guarantee.
Quick start
node build-site.mjs # regenerate public/index.html
node verify.mjs # run the MUST_PASS checks
Then open public/index.html in a browser.
The plan at a glance
- 10 phases, Day 1–730: Foundation → Requirements (SRR) → PDR → CDR →
Component fab → Hot-fire campaign → Integration & stage qual → Launch prep & FAA → Launch & flight → Post-flight.
- 5 crew (E1–E5): systems/CEO, propulsion, structures+avionics+GNC,
manufacturing+test, operations+regulatory.
- 17 milestones from kickoff (Day 1) to flight (Day 710) to program review
(Day 730).
- $200M allocated across propulsion, tooling, structures, test facilities,
avionics, launch/FAA, salaries, and a ~$40M reserve; planned peak spend ~$188M.
Honest status
Verification asserts the plan is internally consistent, complete, and deterministic. It does not assert that a rocket exists or that the schedule is achievable in reality. See proof/LIMITATIONS.md. The authoritative certification state, Evidence Grade, and Trust Score are assigned by the Proof Layer (tools/forge-proof.mjs), not by hand.