FICTIONAL PLANNING ARTIFACT. "Apogee Launch Co." is an invented company. Nothing here builds, tests, or flies a rocket. "To space" means a suborbital flight crossing the Kármán line (100 km); orbital flight is out of scope. All figures are planned targets, not measured results.
FForge Outcome Delivery
Apogee Launch Co. — 24-Month Plan to Space

Reproduce

← Back to case study Open the interactive plan ↗

REPRODUCE — rocket-24-month-plan

Every number in this outcome is reproducible from the plan model with two commands. Requires Node.js >= 20.

1. Reproduce the verification

From delivery-package/rocket-24-month-plan/:

node verify.mjs

This regenerates verification-report.json and verification-report.md and prints each MUST_PASS check with PASS/FAIL. It also rebuilds the website as part of its checks.

2. Reproduce the website

node build-site.mjs

Writes public/index.html. Open it in any browser.

3. Reproduce the proof package

From the repository root:

node tools/forge-proof.mjs --outcome delivery-package/rocket-24-month-plan --verify "node verify.mjs" --report verification-report.json
node tools/forge-proof-verify.mjs --outcome delivery-package/rocket-24-month-plan

The first command re-runs verification, derives claim lineage, and checksums every file. The second self-verifies those checksums.

Determinism

src/plan.mjs is pure and uses UTC date math, so allDays() is byte-identical across runs. verify.mjs asserts this explicitly (the "deterministic" check), so repeated runs produce the same metrics and the same report.

Key numbers and where they come from

NumberSource
730 days plannedallDays().length in src/plan.mjs
10 phases tiling Day 1–730PHASES
17 milestones; FLIGHT at Day 710MILESTONES
$200M allocation (sums exactly)BUDGET_ALLOCATION
Peak spend ~$188M, ~$40M reserveCUM_SPEND_M, BUDGET_ALLOCATION
5-person crewTEAM