recent-discourse-sweep
Run this before a touch, a call, or a bet that depends on what is true this month. Produces a sourced synthesis and a coverage report.
The one-line law
A sweep is only as honest as its coverage report. An empty result means nothing until the venues are proven live.
The play
-
Fix the window and list the venues before searching. Name the window in days, then list every venue you intend to read: open discussion communities, technical forums, video, job postings, filings and preprints, the trade press, short-form social feeds, plain web search. The list is the plan. A venue never listed cannot turn up missing later.
-
Keep the topic string clean. The topic is a routing key, not a description: plain words, no brackets, no slashes, no "versus" unless a comparison is wanted. Disambiguation belongs in the query terms. A topic carrying a parenthetical splits silently into two searches, one of them a fragment, and half the budget goes into the fragment. Before sweeping a named company, product or person, read
references/query-plan.md. -
Run the venues one at a time and record each outcome as one of three states: read-with-results, read-and-empty, never-reached. Three different facts, and collapsing them into "nothing found" is the failure this skill exists to prevent. Diagnosis is in
references/coverage-report.md, to be read the first time a venue comes back empty. -
Date every item and drop what falls outside the window. Sources return older material without announcing it. An undated item is not evidence, it is a guess with a link.
-
Rank by engagement, then read against the ranking. Engagement measures how loud a view was, not how common. Note the dissent that got no traction; it is often the objection a buyer raises on the call.
-
Synthesise into prose, with the source link and the item's own date on every claim. Never hand over raw result clusters or snippet dumps as the answer.