Record the first wrong decision
Keep the question reference, topic, your first incorrect step and a brief error category. Useful categories include missing knowledge, wrong method, misread condition and execution slip. Preserve enough context to reproduce the problem, but avoid copying a full page when a source link and one sentence will do.
Write a repair and a retest
State what you will do differently and how to verify it on a fresh task. Link the relevant explanation or example. 'Be more careful' is not a repair: specify the cue you missed, the check you will perform or the concept you must explain before attempting the next problem.
Revisit, then archive with evidence
Use the log to start later sessions. Attempt before revealing the correction, and record whether the same error recurs on a different problem. Move reliable items out of the active queue while keeping their history. A fixed archive rule should be treated as your workflow choice, not proof that an error can never return.
Worked example
Entry: rates question, missed unit conversion. Correction: convert minutes to hours before substitution. Source: lecture four, slide twelve. Retest: solve a new problem with mixed units and explain the conversion. The next session starts with that task. If successful after a delay, the entry leaves the immediate queue instead of demanding another full rewrite.
Before you finish
- Each entry identifies a specific mistake.
- The repair names an observable action.
- The queue includes delayed retests and a way to retire resolved items.