Module 5: Architecture Decision Records & Reviews: Worked Example Studio
Worked examples make the module concrete. Use this page to create examples that show the reasoning path, not only the final answer.
Required Example Pattern
Every worked example should include:
- Problem statement: the smallest precise version of the task.
- Wrong first attempt: a plausible approach and why it fails.
- Correct reasoning: the invariant, model, tradeoff, or mechanism that actually matters.
- Final solution: code, proof, diagram, query, command, or design note.
- Why it works: short justification tied to module concepts.
- Transfer question: a nearby variant that forces generalization.
Example Slot 1: Foundation
Use this for the first concept cluster. Keep it small enough to complete in 20-30 minutes.
| Section | Notes |
|---|---|
| Problem | |
| Wrong attempt | |
| Correct reasoning | |
| Final solution | |
| Why it works | |
| Variant |
Example Slot 2: Integration
Use this for a problem that combines at least two clusters from the module.
Example Slot 3: Edge Case
Use this for a case where a familiar solution breaks because a precondition changes.
Completion Standard
- At least one example includes a wrong first attempt.
- At least one example includes a visual model, trace, test, or proof.
- At least one example asks the learner to solve a variant without looking at the worked path.