Design Question Map¶
Guide Fit¶
flowchart TD
family["Python Programming"] --> program["Python Object-Oriented Programming"]
program --> pressure["A concrete learner or reviewer question"]
pressure --> guide["Design Question Map"]
guide --> next["Modules, capstone, and reference surfaces"]flowchart TD
question["Name the exact question you need answered"] --> skim["Skim only the sections that match that pressure"]
skim --> crosscheck["Open the linked module, proof surface, or capstone route"]
crosscheck --> next_move["Leave with one next decision, page, or command"]Read the first diagram as a timing map: this guide is for a named pressure, not for wandering the whole course-book. Read the second diagram as the guide loop: arrive with a concrete question, use only the matching sections, then leave with one smaller and more honest next move.
Use this page when the learner problem is easier to name than the module that teaches it.
Question to route table¶
| If the question is... | Start with | Keep this guide open | Capstone cross-check |
|---|---|---|---|
| What kind of object is this, and what contract should it carry? | Modules 01-03 | Module Promise Map | model and lifecycle tests |
| Should this be a value object, entity, service, or policy? | Module 02 | Pressure Routes | domain objects, policies, and adapters |
| How do I stop illegal states from leaking through? | Module 03 | Module Checkpoints | lifecycle APIs and validation surfaces |
| Which object should own a cross-object invariant? | Module 04 | Capstone Architecture Guide | aggregate root, events, and projections |
| Where should retries, cleanup, or recovery behavior live? | Module 05 | Pressure Routes | runtime facade and unit-of-work boundary |
| How do I add persistence without flattening the model? | Module 06 | Capstone File Guide | repository and projection boundaries |
| How do clocks, queues, or async work without corrupting ownership? | Module 07 | Proof Ladder | runtime coordination and tests |
| Do the tests actually prove the intended contracts? | Module 08 | Capstone Proof Guide | test suite and saved review bundles |
| What should be public, internal, or extensible? | Module 09 | Capstone Review Checklist | facade and extension seams |
| Is this design operationally trustworthy? | Module 10 | Proof Ladder | inspect, verify-report, confirm, and proof routes |
How to use it¶
- Name the design question in one sentence.
- Start with the smallest module range that answers that question.
- Keep one guide open so the route and exit bar stay visible.
- Use the capstone only after you can say what you are trying to confirm.