The public shelf

Brief me on a topic I know little about.

Topic: {{topic}}
Why I need to understand it: {{purpose}}
What I already know: {{background:almost nothing}}

Give me:
1. The one-paragraph version: what this is and why it matters.
2. The 5 to 7 core ideas, each explained in two or three sentences, in the order that makes each one easier to understand than the last.
3. Key terms: a short glossary of the words I will keep running into, defined in plain language.
4. How it works in practice: one concrete, realistic example from start to finish.
5. Where the disagreement is: the open questions or debates among people who know this well, and the main positions.
6. Common misconceptions: what beginners usually get wrong.
7. What to read or watch next: the types of sources worth my time, such as a standard textbook, a review article, or an official guide, and what to search for to find them.
8. Five questions I should now be able to answer, so I can test myself.

Rules:
- Aim it at my purpose. Leave out what I do not need for it.
- Separate what is well established from what is contested or changing quickly.
- If part of this may have changed recently, say so and tell me to check current sources.
- Do not invent book titles, authors, papers, or links. If you are not sure a specific source exists, describe the kind of source instead.

Explain the code below so I could confidently change it.

My experience level: {{level:comfortable with programming basics, new to this codebase}}
What I am trying to do with it: {{goal:understand it}}

Structure your answer like this:
1. The big picture, in two or three sentences: what this code is for and when it runs.
2. Inputs and outputs: what it takes in, what it returns or changes, and any side effects such as database writes, network calls, or files.
3. A walkthrough in the order the code runs. Group lines into steps and explain each step, not each line.
4. Anything non-obvious: language features, library calls, or patterns I may not know. Explain each in a sentence or two.
5. Why it is probably written this way, where that is not obvious.
6. Gotchas: assumptions the code makes, things that would break if changed carelessly, and anything that looks like a bug.

Rules:
- Use plain words. When you have to use a technical term, define it the first time.
- If what the code does depends on something I have not shown you, say what you are assuming.
- Do not rewrite the code unless I ask.

Code:
{{code}}