Document your product's RAG architecture
The final step of the course: gather your decisions into a document the team can review, challenge and implement. You consolidate your product's RAG design file with its test set, justifying each choice, then plan the near-term rollout using the templates in the exit kit.
Lesson objective
By the end of this lesson, you will be able to assemble your product's documented RAG architecture in seven sections, with its 30-question test set, and plan its rollout at 7 and 30 days.
Topics covered
- documenting a RAG architecture
- architecture document
- implementation plan
- RAG templates
Where it fits
Test, cost and document
How do I prove my RAG works, what does it cost, and how do I document it?
Lessons in this module
- Build the 30-question test set and diagnose failures
- Cost the RAG system and choose how to build it
- Document your product's RAG architecture (this lesson)
What you will learn in the course
This lesson is part of the course Design a RAG architecture that fits your product
- Choose, for an information need, between long context, data injected by the application, RAG and fine-tuning, and justify the choice by volume, update frequency, access rights and cost.
- Specify the source inventory, exclusions, the metadata to capture and the document chunking strategy.
- Design retrieval: semantic, keyword or hybrid search, reranking, contextual retrieval, number of passages and relevance threshold.
- Specify the answer grounded in sources, how citations are displayed, how conflicting sources are handled and what happens when nothing is found.
- Specify access filtering before the model reads any passage, and index freshness (resync, deletions, versions).
- Build a set of 30 test questions that covers RAG failure modes and diagnose which stage caused a wrong answer.
- Estimate the cost items of a RAG system and choose between a hosted tool, a managed knowledge base, a vector database and a custom build.
Related courses
- Build an AI assistant for your productAdvanced · ~3 hr
- Evaluate an AI feature: test sets, metrics and LLM judgesAdvanced · ~3 hr
- Ship and monitor an AI feature in productionExpert · ~3 hr