Rubric: account-recovery design
Total: 20 points. Assess the student's evidence and explanation, not exact random token values. Copied text and screenshots are equally acceptable. The public worked solution is a teaching reference, not a secret answer key.
| Area | Points | Full-credit evidence |
|---|---|---|
| Observe the starter | 4 | Shows empty-token reset accepted, verifies changed login behavior, and explains why knowing an address is not ownership. |
| Define the design requirement | 5 | Identifies the protected action, unauthorized requester, required proof, intended sequence and unchanged state on rejection; distinguishes the teaching mailbox from a private production channel. |
| Implement the repair | 4 | Correct helper import and server-side guard before password update; does not weaken tests or helpers; explains the update ordering. |
| Verify behavior | 5 | Records rejected reset with unchanged password, legitimate owner recovery, replay rejection, and complete passing check output; distinguishes manual from automated evidence. |
| Explain boundaries | 2 | Gives a relevant additional production protection and explains why dependency scanning alone does not establish the recovery design is safe. |
Award partial credit within each row for demonstrated parts. A passing test transcript without the design explanation cannot earn the design points. An observation-only submission can earn interpretation points but not implementation points without an actual repair; communicate adaptations before class.