Problem Statement
Stage: Product Intent and Acceptance
Research notes list user needs with different frequencies.
Deliverable
A frequency-ranked persona list.
Input and output contract
Read role|need|frequency records and sort by descending frequency, then role.
Acceptance criteria
- Parse integer frequency.
- Use stable alphabetical tie-breaking.
- Print role: need (frequency).
Suggested vibe loop
Read AGENTS.md, connect your Ollama or OpenAI-compatible provider in the browser, and ask the agent to restate the contract and make one small verifiable change. Watch edits stream into app.py while the editor is locked, then review the result and run the visible example. Keep the checkpoint when the evidence is correct or use Undo to restore it. The browser-client agent does not require an administrator gateway or API key.