Define an MVP honestly

When the "minimum" version has quietly grown into the full product.

Define a genuinely minimal first version of the idea below.

1. State the one thing we are trying to learn, and what result would make us stop. If the answer is "we already know it works", say so, and this is not an MVP but a first release.
2. Strip the scope to what is needed to learn that. Challenge each remaining item: what do we lose if it is not there for the first users?
3. List what can be manual, faked, or done by a human behind the scenes at this volume.
4. Name the quality floor. Some things cannot be minimal: data loss, security, and anything that damages trust permanently.
5. Say honestly whether the proposed MVP is actually minimal or just the full plan with the timeline compressed.

The idea:

Prioritising and scope. Deciding what makes the cut and what the plan actually is: backlogs, MVPs, estimates, roadmaps.