Write the problem hypothesis
For [specific user], completing [job] is difficult because [missing capability], causing [measurable consequence].
You can name one user, one situation and one measurable consequence without proposing a feature.UEP: First-class input requests — `input_required` event, `awaiting_input` status, and `POST /v1/responses/{id}/input`
Evidence observed in HarnessRouter/harnessrouter, a Coding project.
2 comments0 positive reactions7 days openProject Radar 88
uep
Start the no-account validation tool4 guided steps · private browser notes · export anytime
REPEATED ACROSS 8 PROJECTS
Related friction appears in 8 independent repositories. This is stronger than one backlog item, but still requires direct user validation.
Project strength and demand confidence are measured separately.SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Reporter context: Problem UHP's task model is fire-and-forget. The task statuses are / / / , and the SSE event vocabulary (lifecycle, output items, text deltas, reasoning, tool-call deltas, error) has no event for "the harness needs an answer to continue." Real harnesses need to ask. The cases are ordinary, not edge cases:…Excerpted from the public Issue. Read the complete thread before interpreting it.
Recruit: Recruit contributors who can replay the problem in a representative repository and development environment.
Guardrail: Use a fixed test case and compare completion, regressions and recovery against the unchanged baseline.
Interview five developers or engineering leads
- When did you last need this?
- What outcome were you trying to reach?
- What did you use instead?
- How often does this occur?
- What commitment would prove it matters?
Run the smallest experiment
Deliver the outcome manually or with a narrow prototype before building a reusable feature.
A user completes the real workflow and commits time, data, distribution or budget to repeat it.Use a fixed test case and compare completion, regressions and recovery against the unchanged baseline.Make a build decision
- Build: repeated pain and active commitment
- Narrow: pain is real but the audience or job differs
- Stop: weak frequency or no behavioral proof
Why this brief exists
Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.