Reference¶

Page Maps¶

graph LR
  family["Python Programming"]
  program["Python Meta-Programming"]
  section["Reference"]
  page["Reference"]
  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"]

This shelf is for durable metaprogramming vocabulary, escalation rules, and review judgment. Use it when the mechanism is already recognizable and you need help deciding whether it belongs at all, where it belongs, or how to prove it cleanly.

Choose the right reference route¶

If your question is...	Best page
What does this term mean locally?	Glossary
Where does this mechanism sit in the course sequence?	Module Dependency Map
What should I practice or prove next?	Practice Map
How should I review this mechanism?	Review Checklist
Which sharper boundary question should I ask?	Boundary Review Prompts
How can I turn this idea into active recall?	Self-Review Prompts
What failure shape am I seeing?	Anti-Pattern Atlas
What counts as genuinely complete understanding?	Completion Rubric
Does this mechanism belong in the course center or at its edge?	Topic Boundaries

What this shelf is for¶

keeping lower-power and higher-power runtime choices distinguishable
reviewing decorators, descriptors, and metaclasses without magic-language shortcuts
connecting module order to practice and capstone proof surfaces
forcing stronger runtime tools to justify their blast radius

Guide set¶

Stop here when¶

you know the lowest honest mechanism for the current problem
you can turn that judgment into one keep, change, or reject call
you know whether the next move is back to a module or into the capstone