Guides

Page Maps

graph LR
  family["Python Programming"]
  program["Python Meta-Programming"]
  section["Guides"]
  page["Guides"]
  capstone["Capstone evidence"]

  family --> program --> section --> page
  page -.applies in.-> capstone

flowchart LR
  orient["Orient on the page map"] --> read["Read the main claim and examples"]
  read --> inspect["Inspect the related code, proof, or capstone surface"]
  inspect --> verify["Run or review the verification path"]
  verify --> apply["Apply the idea back to the module and capstone"]

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 section when you need route guidance rather than a single mechanism page. The guides keep the reading order, proof path, and capstone bridge explicit so the modules do not have to repeat that scaffolding.

Choose one lane

If your pressure is...	Best page	Then go to...
I need the shortest honest entry route.	Start Here	Course Guide
I need the module arc and review bar kept explicit.	Course Guide	Learning Contract
I need to choose a mechanism without skipping lower-power tools.	Pressure Routes	Review Checklist
I need to know what each module is supposed to change.	Module Promise Map	Module Checkpoints
I need to route a runtime claim to evidence.	Proof Matrix	Proof Ladder
The capstone runtime still feels unfamiliar.	Start Here	Capstone
I am resuming after a break.	Mid-Course Map	Proof Ladder

Use the shelf by job

Job	Best page
understand the module arc and support-page roles	Course Guide
see the sequence justified	Module Dependency Map
rehearse the module-to-proof loop	Practice Map
route mechanism choice through the stable review bar	Review Checklist
sharpen a keep, change, or reject decision	Boundary Review Prompts
spot smells before you can name the mechanism	Anti-Pattern Atlas
keep scope boundaries explicit	Topic Boundaries
route a claim to executable evidence	Proof Matrix
choose the smallest honest proof route	Proof Ladder
confirm the local environment before public commands	Platform Setup

Cross into the capstone deliberately

If you need...	Best page
the capstone's role in the course	Capstone
the module-to-repository route	Capstone Map
a bounded first pass through commands and files	Capstone Walkthrough
ownership boundaries inside the runtime	Capstone Architecture Guide
file responsibilities inside the repository	Capstone File Guide
a bounded proof pass	Capstone Proof Guide
structured repository review	Capstone Review Worksheet
safe evolution	Capstone Extension Guide

Good use of this shelf

• Open one route guide first, not three at once.
• Move to reference pages when the question becomes a standard or boundary call.
• Move to capstone pages only after you know which module claim you want to inspect.
• Stop once one page has given you a clear next module, proof route, or review decision.

Keep The Layout Stable

• index.md stays the course home
• guides/ stays the study route and proof shelf
• capstone/ stays the capstone-specific reading, proof, and review shelf
• reference/ stays the durable runtime and review shelf
• module-00-orientation/ plus Modules 01 to 10 stay the course arc

Directory glossary

Use Glossary when you want the recurring language in this shelf kept stable while you move between study routes, proof routes, and support pages.