to-pitchlisted

# to-pitch Run an adaptive interview that turns one bet a founder wants to make into a seven-field pitch artifact, pointed one hop back at the vision it came from, and record it only once the founder explicitly approves. ## Before starting **A pitch is never shaped on an ungated vision.** Before asking the first interview question, check `docs/product/vision.md` — a repo holds exactly one — for its `approved_by`/`approved_at` approval marker. The same single read described below serves both the check and the interview, so this costs no extra visit to the file. Two cases refuse the session outright: - **The approval marker is absent** — either the vision was never approved, or its marker was cleared by an in-place revision. These are one case, not two: `to-vision` clears `approved_by`/`approved_at` in the same write that lands a revision, so a vision mid-edit reads exactly like one never approved, and gets exactly the same refusal. That equivalence is the point. An in-flight vision edit must not leak into a pitch: the pitch would end up pointing one hop back at a customer, or a thesis, that the founder is in the middle of changing, and nothing downstream would show that the ground had moved. - **There is no vision artifact at all** — tell the founder to run `/to-vision` first, and stop. Never author, infer, or stub a vision to get past this check. A vision the founder didn't write and approve isn't a foundation, and inventing one would hide the exact gap this check exists