Turn one reviewed public signal into a candidate research card. Record the user task, source, what it directly shows, its limits, and the next validation step. The card is an editorial handoff for research, not proof of demand, a product recommendation, or an automatic publishing decision.
Build a candidate evidence card
What makes a useful evidence card?
Keep the observation separate from the editorial interpretation. A public discussion can document one person's question; an official guide can document a supported workflow; neither by itself measures how many people have the task. Product Hunt's launch guide asks makers to prepare specific launch information and define goals, while its preparation guide describes multiple possible success measures. That supports recording a task and a follow-up check, not treating a launch signal as broad demand.
How should I validate the candidate?
- Open the source and check that it actually supports the written observation.
- For discussion samples, freeze query wording and date range, inspect relevance, and keep anecdotal examples distinct from representative evidence. The site's HN sampler returns query matches, not a demand estimate.
- For a product profile or comparison, verify changeable feature and access claims against current official documentation and record the check date.
- Publish only when the resulting page can answer a real task with enough sourced detail; otherwise leave the card on hold.
What does this generator not establish?
It does not fetch sources, verify URLs or claims, combine signals, score products, estimate search demand, or publish a page. The user supplies and reviews every field. A well-formatted card can still contain weak or incorrect evidence, so check the original sources before using it.
Frequently asked questions
Does one discussion prove that a topic is popular?
No. It is an example of an observed question. Popularity, search volume, representativeness, and product quality need different evidence.
Does the tool check my source URL or facts?
No. It formats the URL and notes you provide. Open the source yourself and confirm it supports the observation.
Is my card stored or sent to a server?
No. Formatting happens in your browser. The page does not send or save the card; review it for sensitive material before copying it elsewhere.
What evidence supports this workflow?
Product Hunt's official launch guidance describes preparing submission content, asking for feedback, and setting goals. The HN Search API documents a way to retrieve public story and comment matches. These sources support documenting a traceable observation and its limits; they do not show that this generator is in demand or that any topic is popular.
Sources · checked November 3, 2026
Related: sample public HN discussions, review the site's discussion evidence method, and turn a validated task into a coding-agent brief.
Methodology and limitations
This browser-only tool formats user-entered notes and a manually supplied source URL. It does not retrieve or verify evidence, measure demand, score products, or publish content. Product Hunt launch guidance and HN Search API documentation were checked November 3, 2026; these sources support the documented workflow only, not claims that this tool or any topic has measured demand.
Affiliate placeholder {{AFF_TOOLNAME}} — referral link not configured.