Capture link-story images
Turn one public outline slice into link-story images. Do not open a second chapter.
Linking story — a weekly ladder of sessions. Treat the week as a budget for link-story images, 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 link-story images, then add a capped set from the same slice.
Repair link-story images
Rewrite every link-story images that failed twice. It was usually two facts glued together.
Mix link-story images
Let due link-story images from different chapters sit in one queue. Do not re-sort into textbook order.
Audit public outline
Check ten mature link-story images against public outline. Retire anything the outline dropped.
Light new
Halve new link-story images and spend the rest on due reviews plus one closed-book dump.
Sessions
- Due-only sprint — Twenty minutes of due link-story images, no browsing.
- New-item clinic — Thirty minutes to turn one public outline subsection into link-story images.
- 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 link-story images for misses.
- Freeze rehearsal — Run a day with zero new link-story images to feel the true review load before an exam week.
Ladder
- Novice — You can produce a first set of link-story images from one public outline page in a single sitting.
- Stable — Due link-story images stays inside a weekday time box and repairs happen within a week.
- Fluent — You can explain why today's link-story images is due using the method, not "the app said so".
- Exam-ready — New link-story images 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. Linking story: Keep the public outline in view and treat this page as method, not a leaked key.
ScienceMethodDrillsFast passPitfallsToolsStoriesLocale playbook