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
  pressure["Recognize the current design pressure"] --> shelf["Choose one reference surface"]
  shelf --> judgment["Turn it into one explicit design judgment"]
  judgment --> return["Return to the module or capstone"]
  return --> review["Reopen reference only if a new pressure appears"]

This shelf is for durable language, review criteria, and boundary questions. Use it when the pressure is already recognizable and you need a stable reference surface to sharpen a decision.

Do not use this shelf as a substitute for the lesson. If the concept itself is still unclear, go back to the module or capstone page that teaches it. Reference pages are for judgment, not for first exposure.

Choose the reference page by question

If your question is...	Best page	What it should help you do
What does this term mean in this course?	Glossary	keep the vocabulary stable instead of drifting into private definitions
Why does this module come before or after that one?	Module Dependency Map	understand the course order as a learning dependency, not a publishing accident
What should I practice or prove next?	Practice Map	choose the next deliberate repetition instead of rereading passively
How should I review this object or boundary?	Review Checklist	turn design review into explicit criteria
Which sharper ownership question should I ask?	Boundary Review Prompts	expose weak boundaries before they harden
How do I test whether I actually remember this?	Self-Review Prompts	turn reading into active recall
What failure shape am I probably seeing?	Anti-Pattern Atlas	identify recurring design distortions without hand-waving
What counts as genuinely complete understanding here?	Completion Rubric	distinguish familiarity from defensible understanding
Does this topic belong in the center of the course or at its edge?	Topic Boundaries	keep scope honest and stop importing unrelated concerns

What this shelf is good for

Use it to:

• keep ownership, lifecycle, and collaboration language stable
• review object, aggregate, public, and extension boundaries with explicit criteria
• connect module order to practice and capstone proof routes
• detect when a boundary is earning its complexity and when it is only accumulating noise

What this shelf is bad for

Do not use it for:

• first-time learning of a concept the modules have not yet taught you
• passive rereading when you are avoiding exercises or proof
• replacing the capstone when the real question is executable evidence
• pretending a checklist is understanding

If one of those is happening, leave this shelf and return to the lesson or capstone.

Good entry routes by learner need

Learner need	Best first reference page
I need the course vocabulary to stop shifting under me	Glossary
I need to know whether I am practicing the right thing next	Practice Map
I need sharper questions for a fuzzy design review	Boundary Review Prompts
I need to diagnose a recurring design smell	Anti-Pattern Atlas
I need an honest completion bar	Completion Rubric

Strong reference rhythm

1. Name the exact question.
2. Open one reference page only.
3. Turn it into one explicit design judgment or next action.
4. Return to the module, exercise, or capstone.

The reference shelf is working only if it sends you back to real study or review.

Companion pages outside reference

Need	Best page
route selection before the pressure is clear	Guides
course-stage orientation	Course Map
executable system route	Capstone
proof-route selection	Proof Matrix

Exit check

Leave this page only when you can say:

My recognized pressure is ____, the right reference page is ____, and the design judgment or next move it gave me is ____.