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.Evidence observed in THU-MAIC/OpenMAIC, a General AI project.
Related friction appears in 13 independent repositories. This is stronger than one backlog item, but still requires direct user validation.
Project strength and demand confidence are measured separately.Reporter context: Problem The generation pipeline assumes a short lesson. A request that names an hour is planned by the same rules as a request that names fifteen minutes, and the result is one of two failures: A sprint. The scene-count guidance is "1-2 scenes per minute", so an hour becomes 60-120 pages, each with a paragraph of…Excerpted from the public Issue. Read the complete thread before interpreting it.
Recruit: Recruit people who can show a recent, concrete example of the problem.
Guardrail: Measure behavior in the real workflow and keep a human review step for consequential actions.
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.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.Measure behavior in the real workflow and keep a human review step for consequential actions.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.