You already know: agent loops, tools and memory (D9), advanced RAG and multi-hop retrieval (D8), agent security and budgets (D19, D9), evaluation of agents (D10 is next).
Why this matters for Atlas. Agentic RAG replaces a fixed pipeline with decisions: whether to search (some questions the model already knows, some it doesn't), what to search for (decomposing a multi-hop question), when to stop, and what to remember. Done well, it's more accurate and cheaper than searching for everything; done badly, it loops, burns budget, or answers from stale memory with confidence. This capstone builds the decision logic in a simulated environment where accuracy and cost can be measured, then shows the production loop with real tools.
1. When to search: the core decision
The question. Should the agent search for every question?
Start from nothing. Searching costs latency, tokens and money, and can even hurt (irrelevant passages distract). Not searching risks answering from outdated or missing knowledge. An adaptive policy searches when the model's confidence in its own answer is low, when the question concerns recent or private information, or when the answer must be cited. Confidence can come from the model's self-assessment, agreement between sampled answers (self-consistency), or a trained classifier; whichever you use, calibrate the threshold on an eval set by measuring accuracy and cost together.