Capstone Extension Guide¶
Guide Fit¶
flowchart TD
family["Python Programming"] --> program["Python Functional Programming"]
program --> pressure["A concrete learner or reviewer question"]
pressure --> guide["Capstone Extension Guide"]
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 course asks not only "what is this boundary?" but also "where should the next change land?"
Recommended route¶
- Read Capstone File Guide.
- Compare the change you are imagining with Capstone File Guide.
- Use Capstone Review Worksheet to decide what proof must change with the implementation.
What a good answer looks like¶
- you can name the owning package before editing code
- you can explain why another nearby package should not absorb the change
- you can name the proof surface that must evolve with the implementation