Write the problem hypothesis
For [user], the interface fails to expose or render [critical state or action], preventing [job] and causing [workaround].
You can name one user, one situation and one measurable consequence without proposing a feature.[BUG] 5 user-facing HTML routes return 404 (Flask in-app, /channel/1 /subscriptions /playlists /history /contact)
Evidence observed in Scottcjn/bottube, a Marketing project.
9 comments1 positive reactions94 days openProject Radar 85
Start free validation sprint4 guided steps · private notes · cloud sync
SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Reporter context: Summary Live verification at 2026-06-09T23:42+08:00 found 5 additional user-facing HTML routes on that return HTTP 404 with the in-app Flask 404 template ( ), not nginx. These are distinct from #1362 (7 routes), #1367 (14 routes), and #1369 (5 wRTC routes). Affected routes All 5 routes verified live (curl returns 404…Excerpted from the public Issue. Read the complete thread before interpreting it.
Interview five affected users
- Show the exact screen and action where progress stops.
- What did you expect to see?
- Is the underlying data correct?
- Which devices or browsers reproduce it?
- What workaround is used now?
Run the smallest experiment
Prototype one corrected interaction or rendering state and run five task-based usability attempts.
At least four of five users complete the target action without explanation and can describe the resulting state.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.