stage-5-scope-locklisted

Stage 5: lock the MVP scope. Entry condition: V3 + R2 passed or accepted-open, positioning locked. Output: the **MVP Pack** — not a report; the input contract for the build phase. Its quality bar is the **cold-start test**: a brand-new build session reading only the pack can start building without asking anything already decided. Load `method-rules`; read `state.json`. Templates: the `stage-5-scope-lock-templates` skill. All pack files live in `ideas/<slug>/mvp-pack/`. ## 5.0 Entry guard — run this FIRST, before writing anything The pack predicate is not only a label generator at the end; it is the **entry condition**. Run it before any other stage-5 action: ``` node "${CLAUDE_SKILL_DIR}/../../scripts/pack-verdict.js" <idea-dir>/state.json --json --assuming-lock-pass ``` - Verdict is an issuable label (`Validated` / `Hypothesis` / `Pre-feasibility Hypothesis`) → proceed to 5.1. - Verdict is **`NO PACK`** → **stop here.** Do NOT write `mvp-spec.md`, do NOT write a technical design, do NOT materialize `mvp-pack/`, do NOT run the charter ceremony. Write exactly one file, `architecture-risk-preflight.md` (`status: draft`, gate `LOCK`), containing only: the verdict and its reasons verbatim from the tool, the unresolved prerequisites, and any design contradiction already visible from existing artifacts — each item prefixed **`[PROVISIONAL — pending <gate>]`**. Then report to the founder which gate must resolve, and return. **Why this is a hard stop, not a warning** (dogfood ru