The first release should let a defined group complete one useful workflow and give you evidence for the next decision. It does not need every planned feature, but it does need the controls required for its actual use.
Define a small complete outcome Write down the user, the task, the starting input and the result. For example: a service employee finds an approved instruction and can open its source. Define what happens when the information is missing or the person lacks access.
Then separate: - Required for this release: the end-to-end workflow, relevant access controls, failure handling and a way to judge the result. - Can follow later: extra audiences, channels, integrations or convenience features that do not test the core assumption. - Outside scope: activities nobody has agreed to build or operate.
For an AI pilot, decide which examples demonstrate a useful answer, when it should abstain and who handles exceptions. For a transactional product, inspect the completed action and its failure path. A demo alone is not that evidence.
PromptID describes an AI product delivered under a compressed schedule by adjusting feature scope. That is one project's experience, not a standard deadline for your MVP. The MVP service explains the delivery route.
A useful brief: “For [users], the first release must let them [task]. We will decide whether to continue by checking [evidence].”