Run it
What you give it / what you get back
You give it one sentence and, optionally, a list of subreddits. You get back a report onresearch.demand:
| Field | What it is |
|---|---|
report.verdict | A one-line go / no-go summary. |
report.ranked_clusters | The real needs people voiced, ranked by how many different people raised each — not by how viral one post was. Each cluster has a claim, a distinct_author_count, and its quotes. |
report.web_findings | Supporting facts pulled from the web, each carrying its real source URL. |
report.partial, report.caveat | Set when part of the run came up short (see below). |
Want a richer brief first?
mw.research(question) works from one sentence. If you’d rather refine the question,
set success criteria, and let metalworks suggest subreddits before it runs, plan first:
Scope what it reads
Read from more sources
metalworks reads Reddit by default, and can also read Hacker News, the web, or your own data. Name the sources you want for a run:Update a report later
Each run saves what it read, so your research data builds up over time. Collect more, then update the report to see what changed:When the result is thin
metalworks tells you when there isn’t a real opening instead of inventing one. If the demand is weak or a part of the run degraded — say it couldn’t reach the web — the report comes back withpartial=True and a plain-English caveat saying what
happened. The later steps stay honest about it too, rather than building a launch
plan on signal that isn’t there.