Module 1: Domain Analysis & Architecture Design: 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 Capstone Scoping Lab with only a final answer	Capstone Scoping Lab	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 Domain Discovery Workshop with only a final answer	Domain Discovery 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 Architecture Choice Clinic with only a final answer	Architecture Choice Clinic	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 Design Doc and ADR Katas with only a final answer	Design Doc and ADR Katas	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 Problem Selection: Right-Sized, Motivated, Defensible as vocabulary instead of a tool	Problem Selection: Right-Sized, Motivated, Defensible	The explanation names the concept but cannot decide between two cases.	Write one example, one non-example, and the rule that separates them.
Treating Risk Register: The Scariest Unknowns First as vocabulary instead of a tool	Risk Register: The Scariest Unknowns First	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.

Capstone Scoping Lab

Source: practice/01-capstone-scoping-lab.md

For each statement, identify the error and fix it in one sentence:

1. "My capstone is a URL shortener because I want to use Redis."
2. "My risk register has 40 rows -- I'm being thorough."
3. "My MVP is the homepage -- everything else comes later."
4. "Security is a top-3 characteristic for every system."
5. "I'll cut tests if I run out of time."

Domain Discovery Workshop

Source: practice/02-domain-discovery-workshop.md

Identify the error:

1. "Add note" as an EventStorming event.
2. "All my subdomains are core because I'm building every line of code myself."
3. "My glossary has 3 terms -- my domain is small."
4. "Authentication is core because auth bugs are dangerous."
5. "I'll build the glossary at the end when I know what to call things."

Architecture Choice Clinic

Source: practice/03-architecture-choice-clinic.md

Identify the error:

1. "All 10 characteristics are drivers for my capstone."
2. "I'm using microservices because it's the modern choice."
3. "I'll add fitness functions after the code is working."
4. "Availability is always a top-3 characteristic."
5. "My fitness function tests one function for correctness."

---

Repair Protocol

For each real mistake:

1. Reproduce the failure on the smallest example, trace, proof, query, command, or design sketch.
2. Name the hidden assumption.
3. Repair the artifact.
4. Save evidence that changed: failing then passing test, corrected proof step, revised diagram, safer command, benchmark, or review note.
5. 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.