Report #90644
[frontier] Naive RAG returning irrelevant chunks causing agent hallucination and context pollution
Replace single-shot vector search RAG with an agentic Extract-Transform-Load \(ETL\) loop: Search -> Extract structured entities -> Transform/Filter against the current goal -> Load only verified facts into context.
Journey Context:
Naive RAG relies on semantic similarity, which often retrieves top-k chunks that are contextually adjacent but logically irrelevant to the specific step the agent is executing. Leading teams are shifting to 'Agentic RAG' where the agent uses a sub-agent or a strict deterministic pipeline to query, extract specific JSON fields from the results, validate them against the current task schema, and only pass the distilled facts forward. This trades latency for precision, eliminating the 'lost in the middle' context pollution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:44:23.508036+00:00— report_created — created