Capstone Map¶
Guide Fit¶
flowchart TD
family["Python Programming"] --> program["Python Object-Oriented Programming"]
program --> pressure["A concrete learner or reviewer question"]
pressure --> guide["Capstone 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.
This map turns the capstone into a deliberate study surface instead of a single long page. Use it to decide where to go next when you want concrete proof for a course idea.
Capstone route¶
- Start with Capstone for the overall purpose and domain.
- Read Capstone File Guide when you need a code-reading route.
- Read Capstone Review Checklist when you want an explicit review lens.
- Read Capstone Architecture Guide when you are reviewing ownership and boundaries.
- Read Capstone Walkthrough when you want the scenario flow from creation to incident publication.
- Read Capstone Proof Guide when you want the verification route.
- Use the local capstone guides
COURSE_STAGE_MAP.md,PACKAGE_GUIDE.md,TEST_GUIDE.md,TARGET_GUIDE.md,INSPECTION_GUIDE.md, andEXTENSION_GUIDE.mdwhen you need a narrower review surface.
Module-to-capstone bridge¶
| Module | Inspect this first | Best guide | Strongest matching proof route |
|---|---|---|---|
| Module 01 | src/service_monitoring/model.py |
Capstone File Guide | make inspect |
| Module 02 | src/service_monitoring/model.py and src/service_monitoring/application.py |
Capstone Architecture Guide | make PROGRAM=python-programming/python-object-oriented-programming capstone-walkthrough |
| Module 03 | lifecycle rules in src/service_monitoring/model.py |
Capstone Review Checklist | make inspect |
| Module 04 | aggregate events and read-model flow | Capstone Architecture Guide | make verify-report |
| Module 05 | src/service_monitoring/runtime.py and unit-of-work surfaces |
Capstone Walkthrough | make PROGRAM=python-programming/python-object-oriented-programming capstone-walkthrough |
| Module 06 | src/service_monitoring/repository.py |
Capstone File Guide | make verify-report |
| Module 07 | runtime coordination and tests | Capstone Proof Guide | make verify-report |
| Module 08 | tests/ and saved proof bundles |
Capstone Proof Guide | make confirm |
| Module 09 | public entry surfaces and extension seams | Capstone Review Checklist | make proof |
| Module 10 | full review bundle and architecture surfaces | Capstone Proof Guide | make proof |
How to use the bridge¶
- Start from the module you are reading.
- Inspect the named file or surface first.
- Open the matching guide only after the boundary is visible.
- Run the smallest proof route that confirms the current claim.
Review question¶
At any point in the course, you should be able to answer: which capstone page shows the same decision pressure as the chapter I am reading right now, and which local command or bundle proves it?