SHORT COURSE 3 OF 6 · INTERMEDIATE · 4 GUIDED LESSONS
Build answers on evidence.
Search returns candidates. Learn to inspect them, attach the right source, preserve disagreement, and make missing context visible. Keep instructions inside retrieved text from acquiring the authority to control tools.
Where did the answer come from, and is that source enough?
YOUR FIRST STEP
Find a useful piece of information
Explain document chunks, keyword retrieval, embeddings, and the difference between retrieval and generation.
Watch a short video, try the code, then explain what happened. You can pause, turn on captions, or read the lesson instead.
Your JavaScript and local tools really run. Model choices and classroom records are prepared examples, so no API key is needed for these browser labs. The optional SDK project runs separately on your computer with its own setup.
Your course checkpointAfter the four lessons, connect what you learned
Give two records for the same subject different values. Then put a request to publish inside the untrusted-input lesson's note.
Retain both source references when values conflict.
Identify a missing required record instead of filling it with an invented fact.
Use the run trace to show that changing a note does not authorize publishing.
Use your experiment inputs and lab notebooks as evidence. This is a self-review: only lesson questions and checked code cases count toward your progress.
Research into practiceThe ideas behind this short course
Original teaching informed by primary research and official engineering guidance. Our exercises isolate mechanisms so you can test them; they do not reproduce a research system or its reported performance.
Lewis et al. · NeurIPS · NeurIPS 2020
Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks
Combine information retrieval with generation so a model can use external passages while producing an answer.
The paper uses a trained neural retrieval and generation architecture. A keyword lookup illustrates retrieval but neither reproduces that architecture nor proves a retrieved claim true.
Anthropic · 29 September 2025
Effective context engineering for AI agents
Curate limited context, retrieve relevant information, and distinguish compaction, external notes, and separate subagent contexts during longer tasks.
Summaries can lose details. Persistent notes do not change model weights or establish truth, and a larger context window does not guarantee perfect recall.
Google · Agent Development Kit · Reviewed 13 September 2026 · undated documentation
Conversational Context: Session, State, and Memory
Separate the current interaction's events and state from searchable information that can span sessions. Choose services according to the required storage lifetime.
In-memory stores lose data on restart. Stored or retrieved information is not automatically true, relevant, persistent, or safe to share between users.
Microsoft Research · March 2024
Defending Against Indirect Prompt Injection Attacks With Spotlighting
Separating the provenance of retrieved content and user instructions helps address indirect prompt injection.
The paper evaluates particular mitigations and conditions. A classroom filter or trust flag neither implements the full method nor guarantees protection against all attacks.
Want to build with an instructor?Explore the workshop and longer program
Your JavaScript really runs. The model decisions and school data are authored simulations, so you can learn without an API key. Every workspace also includes a separate real SDK example to explore next. Passing the lab’s cases is practice, not proof that an agent is ready for real-world use.