Choose familiar work: approve a document, reserve equipment, publish an announcement or resolve a support request. Use invented data.
| Prepare | Include |
|---|---|
| The promise | Actor, beneficiary, mandate, exact work, result and relevant follow-ups |
| Three views | Product choice → related contracts → actual resources |
| Two changes | One that preserves the promise; one that changes it |
| One interruption | What remains known or owed, and who handles it |
Words and a diagram are enough for the product view. Engineers can add a small implementation.
Before changing the design, predict what each change should affect. Return later and explain one prediction without looking at your first answer.
Bring the promise, diagram, changes and unresolved questions to your reviewer. Kresna judges the exercises in the guided learning setting.
Engineering Depth
Show the meaningful composition and successors. Keep required data inside protected states, and identify facts that must be checked at runtime.
Explain how the design preserves the original work through the interruption. Use your project's normal checks. A different implementation can satisfy the same story.
Your Reflection
What evidence would help your reviewer distinguish a different implementation from a weakened promise?
Notes are browser-local. Export a copy to keep them; they are not submitted or judged.
Worked Discussion
Follow both changes back to the original promise. Point to the decision owner, the admitted work, current checks and remaining obligations. Explain any limit your design does not cross.