Reference Glossary¶
Page Maps¶
graph LR
family["Python Programming"]
program["Python Object-Oriented Programming"]
section["Reference"]
page["Reference Glossary"]
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 glossary belongs to Reference in Python Object-Oriented Programming. It keeps the language of this directory stable so the same ideas keep the same names across reading, practice, review, and capstone proof.
How to use this glossary¶
Read the directory index first, then return here whenever a page, command, or review discussion starts to feel more vague than the course intends. The goal is stable language, not extra theory.
Terms in this directory¶
| Term | Meaning in this directory |
|---|---|
| Anti-Pattern Atlas | the recurring failure catalog for anti-pattern atlas, used to recognize defect shapes before they harden into local folklore. |
| Boundary Review Prompts | the review surface for boundary review prompts, used to turn judgment into explicit keep, change, or reject calls. |
| Review Checklist | the review surface for explicit keep, change, or reject calls about object boundaries and collaboration design. |
| Self-Review Prompts | the review surface for self-review prompts, used to turn judgment into explicit keep, change, or reject calls. |
| Topic Boundaries | the durable rule surface for topic boundaries, used when a design or review decision needs stable language instead of intuition. |