Overview / Methods
How we verify
Each stage has a different evidence level, and the site labels which one an item has reached.
1 · Discovery
A monthly GitHub Actions job queries Crossref (journal articles, filtered by publication date) and date-bounded Google News RSS with route-specific queries from data/routes.yaml. Discovery records are not evidence. Absence from a search is not absence of progress.
2 · Machine triage (DeepSeek flash)
Records are sent in batches to DeepSeek flash (deepseek-flash), which assigns a route, a relevance score, a signal type, a one-sentence summary and a supporting quote. The code then enforces three rules:
- The quote must appear verbatim in the record's title or abstract, or the summary is discarded.
- The route must be one of the defined route ids.
- Leads below a relevance of 0.6 are kept in the data file but not shown.
Each run has a call budget (MAX_LLM_CALLS_PER_RUN). Records already triaged are never re-sent. A full quarter scan used about 45 calls. Only flash is used; no larger model is called.
3 · Evidence check
A human editor selects a lead for a quarterly issue and retains a snapshot of the primary source. Each fact is extracted as a verbatim quote with a locator. Code rejects values not found in the quote, numbers that match only as substrings, and sources dated after the quarter cutoff. Supplier and announcement claims stay labelled as such. Announced or target capacity is never shown as output.
4 · Technical review
Only a named reviewer's signature can approve an issue. The 2026-Q3 edition is evidence-checked but not yet signed, and the site says so on every item. Full-text source snapshots stay in a private research workspace; only quotes and metadata are published.
Labels
peer-reviewed supplier announcement hold machine-triaged. See the glossary.
Contribute
Submit a lead or a correction through GitHub issues. Route content lives in plain YAML under data/, and pull requests are welcome; every new reference needs a resolvable DOI.