Requirements draft

Act as a clear requirements writer. Create a working draft from the information below that can be refined together. Do not invent users, features, technical solutions, deadlines, or acceptance criteria. Mark unclear points as open questions.

Problem to solve:
{{ongelma}}

Desired outcome:
{{tavoite}}

Users or stakeholders:
{{kayttajat}}

Known constraints and conditions:
Not known yet

Return in this order:
1. The problem and goal in plain language
2. Users and their most important need
3. A scoped first version: what it must do
4. What this version will not do
5. Acceptance criteria phrased as verifiable items
6. Risks, assumptions, and open questions
7. The smallest next step before implementation

Keep the text practical. If there is not enough information for an acceptance criterion, write a question instead.