Module 1: Study Systems & Habit Formation: Mistake Clinic
This clinic turns wrong moves into reusable judgment. Use it after each practice page and again before the quiz or checkpoint.
Module-Specific Mistake Radar
Start with these traps. Replace or extend them with real mistakes from your own work.
| Mistake to look for | Where it shows up | Symptom | Repair evidence |
|---|---|---|---|
| Finishing Build Your Study System with only a final answer | Build Your Study System | The work has no failed case, trace, test, proof gap, or design stress point. | Add the smallest broken example and show the repair that changes the result. |
| Finishing Study System Design Workshop with only a final answer | Study System Design Workshop | The work has no failed case, trace, test, proof gap, or design stress point. | Add the smallest broken example and show the repair that changes the result. |
| Finishing Diagnostics and Retrieval with only a final answer | Diagnostics and Retrieval | The work has no failed case, trace, test, proof gap, or design stress point. | Add the smallest broken example and show the repair that changes the result. |
| Finishing 21-Day Implementation Challenge with only a final answer | 21-Day Implementation Challenge | The work has no failed case, trace, test, proof gap, or design stress point. | Add the smallest broken example and show the repair that changes the result. |
| Treating Systems Beat Motivation (PRIMARY) as vocabulary instead of a tool | Systems Beat Motivation (PRIMARY) | The explanation names the concept but cannot decide between two cases. | Write one example, one non-example, and the rule that separates them. |
| Treating Identity-Based Habit Formation (SUPPORTING) as vocabulary instead of a tool | Identity-Based Habit Formation (SUPPORTING) | The explanation names the concept but cannot decide between two cases. | Write one example, one non-example, and the rule that separates them. |
Practice Mistake Checks
Pull any miss from these checks into your mistake log.
Build Your Study System
Source: practice/01-build-your-study-system.md
If your plan still depends on "when I feel ready," then it is not a system yet. If you have no prepared environment and no low-energy version, it is still a wish, not a system.
Diagnostics and Retrieval
Source: practice/02-diagnostics-and-retrieval.md
If you can recognize the concept but cannot generate your own example, the concept is not stable yet. If your metric can be gamed without real learning, the system is pointed at the wrong target.
Seven-Day Habit Reset
Source: practice/03-seven-day-habit-reset.md
Do not track five habits at once. The point is not ambition. The point is visible consistency. Also, do not make the habit so hard that a single busy day destroys the streak.
Review and Adjust Your System
Source: practice/04-review-and-adjust-your-system.md
Do not respond to one bad week by abandoning the system or doubling the difficulty. Review first, then make one small adjustment.
Repair Protocol
For each real mistake:
- Reproduce the failure on the smallest example, trace, proof, query, command, or design sketch.
- Name the hidden assumption.
- Repair the artifact.
- Save evidence that changed: failing then passing test, corrected proof step, revised diagram, safer command, benchmark, or review note.
- Add one retrieval card beginning with Check... before... or Do not use... when....
Mistake Log
| Date | Mistake | Symptom | Root cause | Repair evidence | Retrieval card |
|---|---|---|---|---|---|
| Starter | Pick one radar row above | Explain how it would fail in this module | Name the assumption | Add a counterexample or corrected artifact | Write the card before closing the page |
Completion Standard
- At least five real mistakes are logged.
- At least two mistakes include a counterexample or failing test.
- At least one mistake connects to an older semester skill.
- At least one correction changes code, a proof, a diagram, a command transcript, a query, or a design decision.