radar-pulselisted

# Community pulse — intake only, never evidence Social tells you what people *think* and what is gaining traction before it reaches papers/docs, and it is often the FASTEST place to spot that something official exists (a post links a repo, a release, a paper). Social is not a primary source ��� but it is a discovery accelerator. This skill captures both without corroding the ledger's evidence standard. The platform/channel/profile list lives in `SOURCES.md`; treat it as a seed and curate it by your own judgment — add platforms and accounts that prove useful, drop noise. Don't restrict yourself to a fixed roster. ## Absolute rules (constitutional carve-out — see AGENTS.md Hard rules) 1. Social NEVER becomes trend evidence. It may only: - create `observation_queue` items, marked `unverified` — promotable to a trend ONLY after the claim is confirmed on a primary artifact (paper, repo, release, official doc), via the `radar-source-verify` skill; - feed the community-pulse note surfaced on the dashboard (Phase 3). 2. Never name or quote individuals in the repo. Link the thread/profile and summarise the signal ("a widely-upvoted r/LocalLLaMA thread reports X"). No handles in evidence/queue text beyond the bare URL. 3. Opened-source rule still applies: only log what you actually fetched. ## Method (best-effort via Tavily, no paid APIs) Per run, ITERATE EVERY entry in the source lists at `SOURCES.md` (see "## Source lists" below) — the list is the CONTRACT