Starship Build Engineering System
Outcome Contract
Outcome Contract — Starship Build Engineering System
Customer request (as received)
Build something showing my skills for: **Lead Starship Engineer (Ship Vehicle
Assembly)** — responsible for the production of the Starship airframe
weldment, including the Integrated Payload Volume, the PEZ, Raceway, Tank
Cleaning, and Megabay 2 Stacking. Develop lean manufacturing processes,
factory infrastructure, tools, and documentation for high-rate production;
drive simplicity into vehicle systems; build/maintain build schedules and
detailed work instructions; develop process parameters; coordinate
qualification and acceptance testing.
Interpretation
A focused, runnable build-engineering decision system that demonstrates the core technical competencies the role names — expressed as working software with independently checkable math, not slideware. It models the exact scope (IPV, PEZ, Raceway, Tank Cleaning, Megabay 2 Stacking) and turns a production target into the artifacts a lead build engineer owns.
In scope (delivered)
| Role responsibility | Delivered capability | Module |
|---|---|---|
| Lean manufacturing for high-rate production | Takt time, Ranked-Positional-Weight line balancing, line efficiency, balance delay, smoothness index, throughput, parallel-station sizing | src/lean.mjs |
| Build schedules / detailed work instructions | Critical Path Method (ES/EF/LS/LF, slack, critical path, lead time); balanced stations are the work-instruction skeleton | src/schedule.mjs, src/buildplan.mjs |
| Qualification & acceptance testing; quality partners | Process capability (Cp, Cpk, expected PPM, sigma level) against weld/dimensional specs | src/quality.mjs |
| Create CAD models / prints; tooling; DFMfit | 1-D tolerance stack-up (worst-case + RSS) for assembly fit | src/tolerance.mjs |
| Drive simplicity into vehicle systems (DFM) | DFA design efficiency + before/after part-count and assembly-time reduction | src/dfm.mjs |
| Factory tools & documentation | CLI build-plan generator + live in-browser Build Line Planner | run.mjs, public/tool.html |
Out of scope / honest constraints (seams)
- Notional data. The vehicle model (
src/vehicle.mjs) — operations, times,
weld samples, tolerances, part counts — is self-authored and notional. It is not SpaceX proprietary data, an as-built process sheet, or a measured production figure. It is structured like the real artifact so the tooling is credible, but no real-vehicle claim is made.
- No hardware. Nothing physical was built, welded, or measured. All results
are computed from the model.
- 1-D tolerance only. The stack-up engine is linear (1-D); it does not do
3-D GD&T or Monte-Carlo variation.
- Capability normality assumption. PPM/sigma-level assume a normal,
in-control process.
Success criteria (MUST_PASS)
node verify.mjspasses all checks, each independently hand-checkable.- Every engine is exercised on inputs with known closed-form answers.
- The Proof Layer runs and assigns a certification state from real evidence.
- Every seam above is disclosed in
proof/LIMITATIONS.mdand the report.