Most RAG tutorials show you three boxes and call it a day. These pages show the full pipeline — user to response, auth to audit log, embedding to reranker — wired for a specific industry, with the domain-specific gotchas most candidates only learn by shipping to production. Start with the Anatomy page to understand the generic pattern, then drill into a vertical.
Before the vertical case studies, there's one page that explains how the generic production RAG pipeline works — with two diagrams (architectural and sequence), a 15-step walkthrough, the naive-vs-agentic delta, and a misconceptions FAQ. Read this first and the verticals will read like specializations of the same pattern.
A patient, rigorous walkthrough of the full production pipeline. Two diagrams (architectural + sequence), 15 numbered steps, agentic RAG delta, and a misconceptions FAQ. This is the page I wish existed when I was learning — and it's the page every vertical below is built on.
Each vertical reuses the same generic pipeline from the Anatomy page, but specialized for the data sources, compliance requirements, and failure modes of a specific industry. New verticals are added as new domains become relevant to the work.
Employees asking policy questions (parental leave, PTO, benefits, compliance). Most universal enterprise RAG use case.
Customers asking about their own orders, refunds, subscriptions, account history. Structured + unstructured hybrid.
Students and teachers querying textbook content, lessons, and learning materials across grade levels.
Clinicians and patients querying medical records, drug interactions, and clinical guidelines.
Agents and claimants querying policy terms, claim histories, and coverage rules.
Advisors and clients querying research reports, account positions, and regulatory filings.
Most AI/ML portfolios show you one of two things: a single toy RAG notebook (“LangChain + Chroma + OpenAI, works on a 10-document corpus”) or a thin buzzword list (“experienced with vector databases”). Neither tells a senior hiring manager whether the candidate can actually wire this up for a real enterprise.
Each vertical page walks through the full pipeline for a specific industry with the gotchas that matter for that industry. It's the artifact every senior RAG engineer should have — a concrete, architecture-level answer to “can this be wired up for our domain, and what does it take?”