cornell-noteslisted

# Cornell Notes ## Activation Contract Use when a learning flow captures a micro-lesson as a note: the 10% formal step of the `learning-loop`, or any time the user asks for a Cornell-style note on a concept just studied. Notes live at `.ai/learning/<topic-slug>/notes/NNNN-<lesson>.md`, numbered sequentially from `0001`. Do not use for book-chapter synthesis — that is the `summarize` skill; this skill defines the capture format inside a learning path. ## Hard Rules - Follow `assets/cornell-template.md`: metadata header, Mermaid map, cue/notes table, summary, recall hand-off. - **Cues are retrieval questions**, never topic labels: "What does the filter chain decide per request?" not "Filter chain". Each cue must be answerable from its Notes cell alone. - 3–7 cues per note; notes cells stay concise (2–4 lines each). If a lesson needs more, it is two lessons. - The **Summary is the learner's voice**: ask them to state it in 2–3 sentences and record what they say (lightly cleaned up); never invent it. If they can't, that is a signal — reteach before closing. - Every note embeds at least one Mermaid diagram (`mindmap` for concept overviews, `graph TD` for processes, `sequenceDiagram` for interactions) and cites at least one primary source in the header. - Every cue is handed to `spaced-recall` as a new card, and the note's `Recall hand-off` line lists the card IDs. Cues are also the topic's quiz bank. - Notes are Markdown in English; never HTML. ## Format See `assets/cornell