Executive Evidence — rocket-24-month-plan

Answered under the IRS_AUDITOR standard. This outcome is a **fictional planning artifact**; claims are about the plan's properties, not about real hardware.

1. What exactly is being claimed?

That a complete, day-by-day 24-month program plan for a fictional 5-person, $200M suborbital rocket company has been produced, and that the plan is internally consistent, complete, and deterministic: all 730 days planned, 10 phases tiling the timeline, a $200M budget that balances, valid milestones, a 5-person crew, and a self-contained interactive website embedding the whole plan. No claim is made that a rocket was built or flown.

2. What evidence supports each claim?

The evidence is verification-report.json (every check + detail), produced by verify.mjs running against src/plan.mjs, captured in proof/evidence/verify.log and traced in proof/EXECUTION_TRACE.json. Each metric and check maps to a row in proof/CLAIM_EVIDENCE.json.

3. Can an independent engineer reproduce this claim?

Yes. proof/REPRODUCE.md lists exact commands; node verify.mjs regenerates the report and node build-site.mjs regenerates the site. proof/CHECKSUMS.json pins every shipped file.

4. What assumptions were made?

See assumptions.json and proof/LIMITATIONS.md: "to space" = suborbital (100 km); the 5 staff are augmented by contractors/vendors; test stands and range are leased; no major post-CDR redesign; the budget is an illustrative model.

5. What limitations exist?

It is a plan, not hardware. Schedule feasibility is unverified and disclosed as the top risk. Costs are planned, not quoted. See proof/LIMITATIONS.md.

6. What seams exist?

The whole company and mission are fictional (DISCLOSED_SEAM); no build, test, or flight occurs; orbital flight is excluded. All seams are listed in proof/LIMITATIONS.md and the verification report's disclosedSeams.

7. What was actually executed?

node verify.mjs (which also runs node build-site.mjs) — see proof/EXECUTION_TRACE.json for exit codes and stdout hashes, and proof/evidence/verify.log for the raw output.

8. What was inferred?

Nothing about reality is inferred. The plan's structure is computed, not guessed; where a judgment was made (e.g. phase durations, budget split), it is stated as a planning assumption, not an empirical finding.

9. What remains unverified?

Whether the mission is physically achievable in 24 months with these resources. That is outside what a planning artifact can prove and is disclosed, not implied.

10. What evidence would invalidate this claim?

A failing check in verify.mjs (e.g. a phase gap, a budget that no longer sums to $200M, a milestone outside its phase, or non-deterministic output), or a checksum mismatch from node tools/forge-proof-verify.mjs. Any such result would invalidate the corresponding claim.