The article explains that Retrieval-Augmented Generation (RAG) is a retrieval system, while agents are responsible for action. The author built a distinct layer that explicitly connects retrieval to action, and tested this setup across nine tasks alongside standalone RAG and agent systems.
Enterprise Document Intelligence [Vol. 1 #13] - Putting the patterns together, and why this is what “agentic RAG” should look like The post RAG Workflow and Loop Engineering: The Dispatcher That Decides When to Loop and When to Stop appeared first on Towards Data Science .
I benchmarked raw chat history, vector-only RAG, and a context graph on the same multi-agent conversations. The results exposed a surprising weakness in relational retrieval.
A minimal OpenAI Agents SDK implementation where retrieval becomes a search-read-decide loop The post Agentic RAG: Let the Agent Search appeared first on Towards Data Science .
The article discusses how agentic AI is reshaping the analytics stack by taking over more execution tasks. It raises the question of which responsibilities should remain with human analysts versus AI agents and explores the importance of this distinction. The piece highlights the evolving role of AI in analytics and the need to define clear boundaries between human and machine work.
Increasing context size in RAG systems doesn’t improve accuracy for aggregation tasks—it makes errors harder to detect. In this article, I benchmark retrieval-based pipelines against a deterministic full-scan engine across 100,000 rows and show why computation queries must be routed away from RAG entirely.
Most RAG systems are optimized for answer quality, not cost—and that blind spot gets expensive fast. In this article, I break down a production-ready cost control layer combining semantic caching, query routing, token budgeting, and circuit breaking, achieving an 85% reduction in LLM costs without sacrificing answer quality.
A practical walkthrough using text-to-SQL as the example The post Why I Stopped Using One Agent and Built a Multi-Agent Pipeline Instead appeared first on Towards Data Science .
Enterprise Document Intelligence [Vol. 1 #M2] - Every RAG system is built in three engineering layers stacked on one LLM call: prompt (the call itself), context (what fills the model’s window), loop (when the next call fires and when it stops).
I built four AI retrieval architectures on a laptop and benchmarked them against the same set of documents and questions. Here’s what the results taught me about the trade-offs between plain RAG, grap...
The article argues that well‑designed architecture can inadvertently eliminate signals that tooling relies on, turning a structural issue into a search problem. It highlights how drawing boundaries in systems can strip away essential cues needed by agents. The piece emphasizes the importance of considering signal preservation when designing architecture.
The article explains how to detect a payload that appears correct yet is not, by employing a watchdog pattern in Python. It discusses the challenges that cause many multi‑agent systems to fail even when their evaluations succeed. The post was originally published on Towards Data Science.
The article outlines a framework for constructing Retrieval-Augmented Generation (RAG) pipelines that progressively add complexity as needed to address observed failure modes. It begins with basic lexical and hybrid search techniques, then incorporates reranking and agentic information‑seeking strategies to improve performance. The approach emphasizes that more sophisticated components should only be introduced when simpler methods prove insufficient.