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

Run & Deploy

← Back to case study Open the interactive plan ↗

Run & Deploy

Run locally

Requires Node.js >= 20. From this folder:

node build-site.mjs     # writes public/index.html
node verify.mjs         # runs all MUST_PASS checks, writes verification-report.*

Open public/index.html in a browser. There is no server or dependency to install — the site is a single self-contained HTML file.

Proof Layer (mandatory gate)

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-gate.mjs  --outcome delivery-package/rocket-24-month-plan --action deliver

The gate must exit 0 before delivery, publication, or commit.

Publish (GitHub Pages)

node delivery-package/rocket-24-month-plan/publish.mjs   # builds published/rocket-24-month-plan/
node tools/forge-portfolio.mjs                           # rebuilds published/index.html

Commit and push published/ to main; the deploy-pages.yml workflow deploys the site automatically. The outcome then appears at https://<owner>.github.io/<repo>/rocket-24-month-plan/ and on the portfolio index.

Real-world deployment seams (disclosed)

This is a planning artifact. There is no backend, no database, and no live rocket telemetry. A real program would replace the static plan model with a live schedule/ERP system, supplier and FAA trackers, and earned-value cost data — none of which exist here. See proof/LIMITATIONS.md.