Relax. We're not going to explain this chapter like a textbook — just like a friend talking you through it, in plain, easy-to-follow terms.
Let's think about it this way for a second
Summarizing is packing light for the trip. Dumping is bringing your entire house. A good summary keeps the facts, the dates, and the source. A bad summary sounds pretty but loses the facts. Sometimes it's fine to have the model summarize a whole chat for you. But if you don't read it yourself, you'll end up trusting a bad summary. Writing your own 3-line summary is the safer move on a first attempt.
Let's connect it to everyday life
Dump — the entire syllabus.pdf. Summarize — "Source: syllabus.md / Week 3 / Due Friday / photosynthesis quiz." If you need detail on the next turn, reopen that file. RAG will pull the passage. In the context itself, keep it short. Don't write "definitely" in a summary. If you're not sure, write "check the file for the exact date."
Let's try it out together
Dump: [entire syllabus.pdf]
Summary:
Source: syllabus.md · Week 3
Due: Friday
Topic: photosynthesis quiz
Unsure: exact room number — check fileWrite short summaries with sources attached, instead of long text.5-Minute Try
Write a fake 10-line paragraph. Turn it into a 3-line summary plus source. Note what fact got lost.
One Quick Heads-Up
A wrong summary is more dangerous than the original text — it's shorter, so it's easier to trust.