04. Week 15 — Daily Recall

Use these after skimming 02_explainer.md. Answer aloud. Keep responses short and sharp.

Monday

1. In the house analogy, what are the blueprint, foundation, plumbing, inspection, and move-in day?
2. Why is a capstone harder than five successful isolated components?
3. Opening failure: how did latency go from 5 seconds to 30 seconds?

Tuesday

1. Draw your capstone architecture from memory in five boxes.
2. Which API contract is most likely to be vague in your project, and why?
3. What does failure isolation mean in practice for your design?

Wednesday

1. What is your MVP path, from user input to successful output?
2. Name one thing you will buy, one thing you will build, and why.
3. If you had only two days, what would you cut without guilt?

Thursday

1. Name three system-level evals your project needs.
2. What is your end-to-end latency budget, and which step consumes most of it?
3. What metric would tell you the project is useful, not just functioning?

Friday

1. If retrieval or a tool fails, what is the user-visible fallback?
2. What does your dashboard need to show before you can trust the demo?
3. What principle from this week should carry into Module 16?