Guides¶

Guide Fit¶

flowchart TD
  family["Python Programming"] --> program["Python Metaprogramming"]
  program --> pressure["A concrete learner or reviewer question"]
  pressure --> guide["Guides"]
  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 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.

Pick one guide lane first¶

New learner¶

Reviewer under pressure¶

Builder choosing a mechanism¶

Read these first¶

Start Here for the shortest honest entry route
Course Guide for the module arc and support-page roles
Learning Contract for the teaching bar and review expectations
Module 00: Orientation for the course shape
Runtime Power Ladder for the governing review model

Use These For Study Planning¶

Pressure Routes when you are entering from a real engineering pressure
Reading Routes when you want a paced path through dense modules
Design Question Map when your question is clearer than the mechanism name
Module Promise Map when you want the promise of each module stated plainly
Module Checkpoints when you need to know whether you are ready for the next module
Outcomes and Proof Map when you want learner outcomes tied directly to evidence
Mechanism Selection when you need a concrete "use this, not that" guide
Module Dependency Map when you need the sequence explained
Practice Map when you want the module-to-proof loop in one place

Use These For Commands And Proof¶

Command Guide for the executable route
Proof Ladder when you need the smallest honest command for the current question
Review Checklist when you need the stable review bar
Self-Review Prompts when you want learner-side comprehension checks
Boundary Review Prompts when you need sharper keep/change/reject prompts
Topic Boundaries when you need the scope boundary
Anti-Pattern Atlas when you need a symptom-first failure map
Glossary when the vocabulary itself is the blocker

Use These For Capstone Reading¶

Capstone Guide for the capstone’s role in the course
Capstone Architecture Guide for ownership boundaries inside the runtime
Capstone Map for the module-to-repository route
Capstone File Guide for file responsibilities
Capstone Walkthrough for the guided first pass through commands and files
Capstone Proof Checklist for a bounded proof pass
Capstone Review Worksheet for structured repository review
Capstone Extension Guide for safe evolution

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 learner 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 teaching 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.