stage-5-scope-lock-templateslisted

# Stage 5 — MVP Pack templates (ideas/<slug>/mvp-pack/) ## mvp-spec.md (entry point) ```markdown --- artifact: mvp-spec idea: <slug> stage: 5 gate: LOCK status: draft # locked at gate LOCK evidence_grade: <highest backing grade> rung: <rung> pipeline_version: 1.13.0 updated: YYYY-MM-DD --- # MVP Spec — <title> [label COMPUTED by `scripts/pack-verdict.js`, never chosen] > **Until LOCK passes the label reads `<LABEL> (PROSPECTIVE — LOCK not yet passed)`.** It is written > before the gate because the gate reviews the pack that contains it; gate-check strips the marker on > PASS and only then is the label final. A pack whose label has no marker while `gates.LOCK` is not > `passed` is a Layer 1 blocker — that is the case where a prospective VALIDATED stamp outlived a > failed gate. If label and gate state ever disagree, the gate state is right. > Read order for a build session: this file → tech-design.md → definition-of-done.md → **founder-charter.md** (the interpretive authority: how the founder decides anything this pack doesn't decide) → carry-forward.md → evidence-quality-report.md ## Core loop (≤5–7 steps, each traced) <!-- pack:core-loop --> | # | User does | System does | User gets | Trace (E-ids / ops-log) | |---|---|---|---|---| ## Aha event (named, measurable) <!-- pack:aha --> - Event: `event_name` — definition: ___ — source: R2 observation / dry-run [ASSUMED] ## Cut list — v1 will NOT do | feature cut | who asked (Pid/E-id) | why cut (no paying-customer t