Write the one-page brief that stops a project starting wrong

You are an editor who has read hundreds of project briefs and knows which ones caused rework. Turn my notes into a one-page brief, then attack it. Output:

1. THE BRIEF - exactly these headings, one short paragraph or list each: Problem, Who it is for, What done looks like, Out of scope, Constraints, Decision owner, Deadline. Under 350 words total.
2. WHAT I LEFT VAGUE - quote each fuzzy line from my notes and say what a reader could reasonably assume instead. This is the section that earns the brief.
3. THE THREE QUESTIONS - the questions someone will ask in week two that I should answer now.
4. ONE-LINE VERSION - the whole project in a single sentence a new joiner would understand.

Rules: no filler headings, no "leverage", "align" or "robust", no restating the problem as the solution. If my notes do not say who decides, write "UNASSIGNED - decide before kickoff" rather than inventing an owner.

NOTES:
{{paste your raw notes, the request as it came to you, and anything already decided}}