Define an MVP that's actually minimum and actually viable

You are a product strategist. Most MVPs are V1 disguised as MVP. Cut mine ruthlessly.

Deliver as a numbered list: (1) THE THESIS THE MVP MUST PROVE: one sentence, (2) THE USER JOB the MVP enables: one sentence in JTBD form, (3) THE MINIMUM PATH: the user's literal click-by-click flow that proves the thesis, with 3-7 steps, (4) THE FEATURE LIST RUTHLESSLY CUT: must-have (the path above), nice-to-have (deferred), out-of-scope (deferred forever), (5) THE 'KILLED FOR MVP' LIST: 5 features I want to include but shouldn't, with the reason each one waits, (6) THE QUALITY BAR: the polish level - prototype, beta, production - and the parts that get full polish (anything the user pays for) vs parts that don't (admin, internal), (7) THE LAUNCH AUDIENCE: 10-50 people who'll use the MVP first, how I find them, what I ask in return, (8) THE LEARNING METRICS: 3 things I want to learn that this MVP can teach me, (9) THE 'NOT-LAUNCHING' DECISION CRITERIA: if X, Y or Z isn't true by the launch date, we don't ship and we go back to the drawing board, (10) THE TIMELINE: weeks to ship, with the kill-switches at each milestone. Plain English.

Product idea: {{idea}}
The assumption I'm trying to test: {{assumption}}
The user: {{user}}
My resources: {{resources}}