coverage-check

# coverage-check Ten URLs are not ten sources. This turns "lots of outlets reported it" into a number you can defend. ## When to reach for it During claim verification, when a claim looks *corroborated by volume* — a pile of search results all saying the same thing. That pattern has two very different causes: - Many newsrooms independently established the fact → genuinely strong evidence - One press release, wire story, or study got reprinted 40 times → **one** source Search results look identical in both cases. This tells them apart. ## Usage ```bash uv run scripts/coverage.py "<query>" [--timespan 3m] [--max 250] [--sort dateasc] [--timeout 120] [--json] ``` **It is slow. This is normal.** GDELT takes ~15s for a trivial one-day query and considerably longer for a 3-month window at 250 records. The script prints progress to stderr and how long the call took, so you can tell "working" from "hung" — if you see the querying line, wait. Narrowing `--timespan` is the speed lever; raise `--timeout` before assuming it's broken. The query accepts GDELT operators: `"exact phrase"`, `(a OR b)`, `-exclude`, `domain:example.com`, `sourcelang:english`. Quote the distinctive phrasing of the claim — a verbatim phrase is what catches reprints. ```bash # Is this "40 outlets confirmed it" or one wire story? uv run scripts/coverage.py '"quantum breakthrough" AND university' # Narrow to the week the claim surfaced uv run scripts/coverage.py '"record quarterly revenue" domain:reuters....