FForge Outcome Delivery
Starship Build Engineering System

Run & Deploy

← Back to outcome

Run & Deploy — Starship Build Engineering System

Prerequisites

  • Node.js >= 18 (uses only the standard library; no dependencies to install).

Run locally

cd delivery-package/starship-build-engineering
node run.mjs            # build plan
node verify.mjs         # verification suite (18 checks)

Open the live planner with no server:

# just open the file in a browser
public/tool.html

or serve the folder if you prefer a URL:

npx --yes serve public   # then open the printed http://localhost:PORT

Deploy (static)

public/tool.html is a single self-contained file (inline CSS + JS, no network). It deploys to any static host — GitHub Pages, S3, nginx — by copying the file. The published portfolio build (node publish.mjs from the repo, per the Forge pipeline) renders this tool at published/starship-build-engineering/.

Plug in real data (removing the seam)

The math engines (src/*.mjs) are data-agnostic. To run against real inputs, replace the notional values in src/vehicle.mjs:

  • ASSEMBLY_OPERATIONS — real manual work-content times and precedence.
  • BUILD_FLOW — real phase durations for the lead-time CPM.
  • WELD_SPECS — measured throat/feature samples and print limits.
  • TOLERANCE_STACKS — real datum chains and gap limits.
  • DFM_CASES — actual before/after part counts and assembly times.

Re-run node verify.mjs and node run.mjs; the structural checks (1–17) are data-independent and keep guarding the math, while the synthetic benchmark becomes a real benchmark on your data.