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