Beginner entry
Basic computer use and light command-line familiarity are enough. If Python is new, use the optional bridge first.
Beginner-entry, engineer-exit. Learn each idea in plain English, build it, break it on purpose, diagnose the failing layer, then apply production controls for evidence, security, evaluation and operations.
0 of 18 curriculum modules completed · 0/18 currently published modules complete · 0 with lab + knowledge-check evidence.
The course keeps the entry barrier low without lowering the engineering exit standard.
Basic computer use and light command-line familiarity are enough. If Python is new, use the optional bridge first.
One running “Evidence Desk” assistant grows across all 18 modules, so each new concept has context.
Finish able to design, evaluate, diagnose, secure and operate retrieval-grounded knowledge systems with defensible evidence.
Every module repeats the same learning rhythm so a beginner always knows what to do next.
Understand RAG, build the smallest loop, preserve source identity and learn chunking without assuming ML knowledge.
Add embeddings, vector search, metadata filters, hybrid retrieval, reranking and safe query transformation.
Engineer context, grounding, citations, source authority, evaluation and failure attribution.
Operate freshness, security, bounded advanced retrieval and a release-gated production capstone.
A real 45–60 minute bridge covers the exact Python patterns used by the course: variables, lists, dictionaries, functions, files, JSON, HTTP and virtual environments.
Every technical term starts with a concrete mental model before implementation detail.
Open Python bridge →Core labs use local Python and inspectable evidence before optional models, vector databases or framework abstractions.
Use the course glossary whenever terms such as embedding, top-k, reranker, provenance or faithfulness are unfamiliar.
Open glossary →The downloadable pack keeps the required path Python-only and inspectable, then includes an optional Ollama practicum for real embeddings and local generation.
13 runnable checks cover the course progression from evidence-first retrieval through security and release gating.
Download RAG lab packUse a local embedding model and chat model through Ollama's REST API while preserving source-labelled evidence, citations and abstention.
Concepts are taught independently of a specific vector database or orchestration framework so the engineering transfers across stacks.
Production RAG is a pipeline. A convincing answer can still be wrong because ingestion, retrieval, filtering, context, generation or citation failed.
Learner-facing titles explain the idea simply; engineering focus and stage show how depth increases.
Engineering focus: Why RAG exists
Understand why an LLM can sound confident yet still need external evidence, and learn the simplest mental model for retrieval-augmented generation.
Open module →Engineering focus: Build the smallest working RAG loop
Build a tiny retrieval-and-generation flow so the architecture becomes concrete before introducing embeddings or vector databases.
Open module →Engineering focus: Turn files into usable evidence
Learn how files become trustworthy knowledge objects with identity, text, metadata and parsing status.
Open module →Engineering focus: Split knowledge without losing meaning
Learn why chunking exists, how chunk size and overlap change retrieval, and how structure-aware chunking preserves context.
Open module →Engineering focus: Search by meaning, not only words
Understand embeddings conceptually first, then learn similarity, model identity and why embedding choice must be evaluated on your corpus.
Open module →Engineering focus: Retrieve semantically similar chunks
Build a small vector index, understand top-k retrieval, and learn why nearest-neighbour search needs filters and evaluation.
Open module →Engineering focus: Retrieve the right evidence for the right user
Use metadata to constrain retrieval by source, tenant, version, date, language or authorization boundary.
Open module →Engineering focus: Combine exact words with meaning
Learn when lexical search and semantic search complement each other, and combine rankings without assuming one retriever is always best.
Open module →Engineering focus: Improve what reaches the model
Use candidate generation, reranking, query rewriting and decomposition to improve evidence quality without hiding the original question.
Open module →Engineering focus: Build the evidence package the model actually sees
Select, order, deduplicate and budget retrieved evidence so the model receives useful context rather than a dump of search results.
Open module →Engineering focus: Make answers show their evidence
Design outputs that distinguish supported answers from unsupported guesses and make citations useful for verification.
Open module →Engineering focus: Know which source should win
Handle stale documents, superseded policies and conflicting evidence using explicit source authority and lifecycle metadata.
Open module →Engineering focus: Measure retrieval and answer quality separately
Build a labelled evaluation set and use retrieval metrics plus grounded-answer checks so improvements are measurable rather than anecdotal.
Open module →Engineering focus: Find the layer that actually failed
Use traces and evidence inspection to distinguish ingestion, retrieval, reranking, context, generation and citation failures.
Open module →Engineering focus: Keep the index synchronized with reality
Design ingestion, updates, re-indexing, deletion and freshness checks so the knowledge system does not quietly serve stale evidence.
Open module →Engineering focus: Treat retrieved content as hostile until proven otherwise
Protect the pipeline from malicious documents, cross-tenant leakage, unsafe tool influence and policy bypass.
Open module →Engineering focus: Use more steps only when the problem needs them
Learn routing, query decomposition, iterative retrieval and GraphRAG concepts without turning every RAG flow into an uncontrolled agent.
Open module →Engineering focus: Build, evaluate, secure and operate the complete system
Integrate ingestion, retrieval, reranking, grounding, evaluation, security, freshness and observability into one production-shaped knowledge assistant.
Open module →FREE
All 18 modules and guided core labs are open learning content.
FREE
30 randomized questions, 35-minute server timer, pass ≥75%, maximum 2 attempts per 24 hours; every attempt contains scenario/application questions.
FREE
Complete all modules, labs and checks to request the self-paced completion credential.
Request completion certificateOPTIONAL · ₹499 incl. GST
Records successful GNU Group Learning Academy assessment completion. It is not vendor accreditation or a professional licence.
Use lifecycle risk discipline: govern, map, measure and manage rather than treating trust as a prompt-only concern.
NIST reference ↗Treat prompt injection, poisoned knowledge, sensitive-data exposure and vector/embedding weaknesses as system threats.
OWASP reference ↗Measure retrieval and answer grounding separately; examples include Recall@k/MRR plus context precision/recall and faithfulness-style metrics.
Ragas reference ↗Graph-based local/global retrieval is taught as an advanced pattern, not as a default replacement for simpler retrieval.
GraphRAG reference ↗Questions emphasize architecture decisions, retrieval failures, evaluation interpretation, security and production operations—not acronym memorization.
84-question bank · 30-question attempt · 35 minutes · pass ≥75% · at least 14 scenarios/application questions.
Ingest and version documents, retrieve with lexical + semantic signals, rerank, preserve provenance, cite sources, abstain when evidence is insufficient, test ACLs and prompt injection, evaluate retrieval and answer quality, exercise the HOLD path, and produce a promote/hold dossier.