A retrieve-then-generate pipeline grounds each response by mechanically searching an organizational index with the raw user message, then placing the returned documents into the generation context. This fixed sequence works when the message is self-contained, but it cannot interpret conversational context, reformulate queries, decide whether retrieval is necessary, or retry with another search. section 10.5
Where the pipeline breaks
A request such as “What is our vacation policy?” can serve as its own search query. After discussing Q2 planning, “And what did the engineering team commit to?” lacks the keywords needed for reliable retrieval because the pipeline ignores conversation history. section 10.5

