The why: the problem being solved, who it's for, and what success looks like. This is what a new teammate — or a new agent — reads first to understand why the project exists, before the what (Blueprint) or the how (Architecture).
No vision doc found yet — add a "## Vision" section to docs/brief.md in the project's workspace.