AutoIndex lifts CRUMB recall by 8.4% without changing retrievers or embeddings
mrdrozdov · x · 2026-07-22
AutoIndex does not settle on a single universal preprocessing recipe. Instead, it learns corpus-specific programs that can slice, normalize, enrich, reweight, and reorganize documents.
The point is not to find the best chunk size. It is to learn the representation program that exposes the most useful evidence to the retriever. To isolate that effect, the rest of the retrieval stack is kept fixed: BM25 retriever, ranking function, and indexing backend remain unchanged. Only the program that maps documents into indexed units is learned.
On CRUMB, that setup yields:
- Recall@100: +8.4%
- nDCG@10: +8.3%
The authors highlight that this is a meaningful gain without retriever fine-tuning, embedding updates, or online feedback.
Related event: AutoIndex Framework Proposes Optimization via Representation Programs(8 posts)→
More from coding & agent
- Dev torn on Cloudflare Agents SDK: full primitives but vendor lock-in — MikkoH · 2026-09-11
- Team-level AI agents: where should shared context and history live? — Al_Grigor · 2026-09-11
- Trust layer for money-moving AI agents: out-of-mandate actions can't get signed — Arpitbuilds · 2026-09-11
- Chaining dependent MCP tool calls: no rollback, duplicate risk — agentrsdg · 2026-09-11
- DeepMind-led paper makes design docs the source of truth, code disposable — SMART regenerates in 1.5-3h for ~$100 — Roger_M_Taylor · 2026-09-11
- Agent-built classifier labels 192k docs for $0.70 vs $13-26 with frontier LLMs — vanstriendaniel · 2026-09-11