Reference¶

Page Maps¶

graph LR
  family["Python Programming"]
  program["Python Object-Oriented 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 object-oriented vocabulary, ownership questions, and review standards. Use it when the design pressure is already recognizable and you need a stable reference surface for making or reviewing a boundary decision.

Choose the right reference route¶

If your question is...	Best page
What does this term mean locally?	Glossary
Where does this design pressure sit in the course sequence?	Module Dependency Map
What should I practice or prove next?	Practice Map
How should I review this object boundary?	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 question belong in the course center or at its edge?	Topic Boundaries

What this shelf is for¶

keeping ownership, lifecycle, and collaboration language stable
reviewing object, aggregate, and extension boundaries with explicit criteria
connecting module order to local practice and capstone proof routes
deciding whether a boundary earns its complexity or should be simplified

Guide set¶

Stop here when¶

you know which object or layer the current question belongs to
you can turn that page into one explicit design judgment
you know whether the next move is back to a module or into the capstone