# Collection Run: 2026-07-08 arXiv Expanded Sweep

status: completed

## Scope

- source: arXiv API
- date window: 2025-07-08 to 2026-07-08
- query groups: 15
- unique candidates seen: 1506
- high-relevance candidates promoted to paper items: 970
- remaining reserve candidates: 536
- new paper files written in this run: 968

## Query Groups

- llm-agent
- language-agent
- ai-agent
- agentic-ai
- agent-evaluation
- agent-memory
- tool-use
- function-calling
- coding-agent
- web-gui-agent
- multi-agent-llm
- agent-safety
- rag-agent
- planning-agent
- autonomous-agent-llm

## Outputs

- `data/arxiv-agent-candidates-2025-07-08-to-2026-07-08.json`
- `data/arxiv-agent-papers-2025-07-08-to-2026-07-08.json`
- `papers/corpus-summary-2026-07-08.md`
- 968 generated `papers/items/*.md` files

## Method Notes

- The candidate manifest stores title, arXiv URL, authors, categories, dates, matched query groups, auto topics, score, and relevance.
- It intentionally does not store abstracts, to avoid turning the repo into a raw abstract mirror.
- Generated paper items are `queued`; they are collection records, not reviewed summaries.
- Auto tags are recall-oriented and need later cleanup.
- The first API pass selected the top 400; after inspecting score distribution, all 970 `relevance=high` candidates were promoted locally from the candidate manifest.
- arXiv returned 429 during a later refresh attempt, so the collector now includes retry/backoff controls and the promotion step can run offline.

## First Trend Takeaways

- Evaluation and benchmarking dominate the corpus.
- Memory is now a central systems topic, including governance, poisoning, provenance, and procedural memory.
- Agent safety has moved toward runtime risks: tool leakage, prompt injection, data injection, memory poisoning, and action-boundary violations.
- Coding-agent evaluation is moving beyond single-issue SWE-Bench tasks.
- GUI/computer-use agents and workflow/enterprise agents are now large enough to deserve separate tracks.
