Every claim in a Straced briefing traces to a source in that day's prep file. Primary sources take precedence over secondary coverage. Aggregators, newsletters summarising other newsletters, and marketing content are excluded.
The fetch runbook searches the last 24 hours across the AI stack each morning. For model releases, API updates, and research papers, it reads the primary source directly — the official blog post, arXiv abstract, or GitHub release page — not secondary coverage.
Technical claims (benchmark scores, pricing figures, context window sizes, parameter counts) are only included in a briefing if they appear verbatim in the primary source snippet. If a figure is not in the prep file, the briefing uses qualitative language instead.
The curate runbook does not use web search during synthesis. The prep file is the only permitted data source. This keeps every claim traceable to a specific fetch run.
News
- The Verge (AI)
Used for breaking announcements when primary source is unavailable.
- Ars Technica
Technical depth. Used for developer-relevant coverage.
Official blog
- OpenAI Blog
Primary source for OpenAI model releases and API updates.
- Anthropic News
Primary source for Claude releases and Anthropic research.
- Google DeepMind Blog
Primary source for Gemini and DeepMind research announcements.
- Meta AI Blog
Primary source for Llama releases and Meta AI research.
- Mistral AI Blog
Primary source for Mistral model and API updates.
Official releases
- GitHub Releases
Release notes for open-source AI tooling. Preferred over secondary coverage.
Research
- arXiv (cs.AI, cs.LG, cs.CL)
Pre-print research papers. Used for benchmark data and technical claims only when citing the actual paper.