Auditor Objections — rocket-24-month-plan

Pre-written hostile objections, each answered from evidence.

Objection 1: "You claim to have built a rocket company."

Response. No. The deliverable is explicitly a planning artifact for a fictional company. Every document, the website header, the verification report, and LIMITATIONS.md state this. No claim of real hardware, funding, or flight is made anywhere.

Objection 2: "24 months to space with 5 people is impossible, so the outcome is false."

Response. The outcome is a *plan*, and its claims are about the plan's internal consistency — not about real-world achievability. Feasibility is explicitly disclosed as unverified and listed as the top risk (LIMITATIONS.md, risk register). The artifact never asserts the schedule will succeed.

Objection 3: "The budget numbers are made up."

Response. Correct, and disclosed: the budget is an **illustrative planning model** (assumptions.json, LIMITATIONS.md). The verifiable claim is narrower and checked: the allocation sums to exactly $200M, the spend curve is monotonic, and it stays under the cap with reserve. Those are arithmetic properties of the model, proven by verify.mjs.

Objection 4: "'Plan every single day' — you probably skipped days."

Response. verify.mjs asserts allDays().length === 730 with contiguous, unique indices, that the phases tile Day 1–730 with no gaps, and that the website embeds all 730 days. Open the planner and browse any of the 24 months.

Objection 5: "The website could be a static screenshot."

Response. The site embeds the full plan as inline JSON and renders the day-by-day planner with vanilla JS; verify.mjs checks for "totalDays":730 and the planner markup in the built file. It is self-contained and runs offline.

Objection 6: "Could another engineer reproduce this?"

Response. Yes — REPRODUCE.md gives exact commands. The model is pure and deterministic (UTC date math), so output is byte-identical across runs, and CHECKSUMS.json pins every file. node tools/forge-proof-verify.mjs re-checks integrity.

Objection 7: "You're hiding the weak parts in footnotes."

Response. The scope and weaknesses are surfaced in the page header banner, the README, the verification report's disclosedSeams, and a dedicated LIMITATIONS.md. They are stated up front, not buried.