Capture meaningful chunks
Turn one public outline slice into meaningful chunks. Do not open a second chapter.
Chunking — a weekly ladder of sessions. Treat the week as a budget for meaningful chunks, not a festival of new items.
Scores here are relative ranks inside this atlas, not lab grades or official cut scores.
Week
Due before new
Finish due meaningful chunks, then add a capped set from the same slice.
Repair meaningful chunks
Rewrite every meaningful chunks that failed twice. It was usually two facts glued together.
Mix meaningful chunks
Let due meaningful chunks from different chapters sit in one queue. Do not re-sort into textbook order.
Audit public outline
Check ten mature meaningful chunks against public outline. Retire anything the outline dropped.
Light new
Halve new meaningful chunks and spend the rest on due reviews plus one closed-book dump.
Sessions
- Due-only sprint — Twenty minutes of due meaningful chunks, no browsing.
- New-item clinic — Thirty minutes to turn one public outline subsection into meaningful chunks.
- Repair surgery — Fifteen minutes: split, add a cue, or move the item off infinite grind.
- Closed-book dump — From memory, list this week's high-yield names, then only flip meaningful chunks for misses.
- Freeze rehearsal — Run a day with zero new meaningful chunks to feel the true review load before an exam week.
Ladder
- Novice — You can produce a first set of meaningful chunks from one public outline page in a single sitting.
- Stable — Due meaningful chunks stays inside a weekday time box and repairs happen within a week.
- Fluent — You can explain why today's meaningful chunks is due using the method, not "the app said so".
- Exam-ready — New meaningful chunks is frozen before a sitting and the remaining work is almost all retrieval.
Educational atlas — not an official syllabus, medical advice, or leaked item bank. Chunking: Keep the public outline in view and treat this page as method, not a leaked key.
ScienceMethodDrillsFast passPitfallsToolsStoriesLocale playbook