explainlisted

Produce one Markdown note in the user's Obsidian vault. Assume the reader knows nothing about the subject. They read it in a few minutes and come out with: - **Why** it exists: the motivation and the decisions. - **How** it works: the architecture, the key mechanisms, the non-obvious parts. The note is done when every rung carries a worked example, every mechanism you cut carries a link in **Sources**, and every number on the note traces to something you ran or quoted. ## What the note is for Three ideas decide everything else. **It serves a mission.** The user asked for a reason - to review a change in that area, to debug something, to stop nodding along in a meeting. Infer the reason from how they asked. The mission decides what goes on the note, and what stays off it. Without a mission the note drifts into a generic overview, which is this skill's main failure mode. **It builds fluency, not retention.** The reader needs to hold the subject now. One read cannot build long-term recall, so spend every line on the subject itself. **It starts from zero.** Assume no prior knowledge of the subject, and none of its prerequisites. The reader is sharp and knows their own field. They may have never heard the word in the title. Every step anchors to a step already on the note. Five unanchored concepts explain nothing. ## Depth ELI5 at the entry point and in tone. Far past ELI5 in substance. Deliberately short of exhaustive. Calibrate to this: the reader can hold the subject,