Tech
Standard RAG vs. Agentic RAG: Moving Retrieval From Pipeline Stage to Runtime Decision
The assumption every RAG demo makes
Standard RAG assumes the user's question maps onto one vector search. One query in, one embedding, one top-k lookup, one answer.
That assumption holds up in demos, because demos ask demo questions. "What's our parental leave policy?" is one document. Retrieve it, stuff it into the prompt, done.
Then you ship, and a real user types: "Did the carrier rate change we approved in Q2 actually reduce our cost per shipment in the Northeast, and does that ho...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to