Module Glossary

Glossary Fit

flowchart TD
  directory["This directory"] --> glossary["Glossary"]
  glossary --> terms["Stable local terms"]
  terms --> reading["Reading and examples"]
  terms --> practice["Exercises and review"]
  terms --> proof["Capstone proof and discussion"]

flowchart TD
  pressure["Hit an unfamiliar term"] --> lookup["Open the glossary entry"]
  lookup --> confirm["Match the term to the local meaning"]
  confirm --> return["Return to the lesson or guide"]
  return --> reuse["Reuse the same wording in notes, code review, and proof"]

This glossary belongs to Module 05: Resources, Failures, and Safe Evolution 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
Copying and Versioning of Objects and Aggregates Over Time	the module's treatment of copying and versioning of objects and aggregates over time, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Design Smells and Refactoring Patterns in OOP Python	the module's treatment of design smells and refactoring patterns in oop python, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Deterministic Cleanup and Leak Prevention in Pure Python	the module's treatment of deterministic cleanup and leak prevention in pure python, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Domain Errors, Recovery Contracts, and Compensating Actions	the module's treatment of domain errors, recovery contracts, and compensating actions, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Evolution Basics and Compatibility Contracts	the module's treatment of evolution basics and compatibility contracts, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Idempotent Operations and Safe Retries (Sync-Only Context)	the module's treatment of idempotent operations and safe retries (sync-only context), used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Logging and Error Propagation as Part of Object Contracts	the module's treatment of logging and error propagation as part of object contracts, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Public vs Internal Modules and Facades for OOP Codebases	the module's treatment of public vs internal modules and facades for oop codebases, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Refactor 4: Introduce New Feature, Preserve Old Behaviour, Document Smell Fixes	the module's treatment of refactor 4: introduce new feature, preserve old behaviour, document smell fixes, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Resources and Context Managers: Objects That Own Things	the module's treatment of resources and context managers: objects that own things, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.
Unit-of-Work: Grouping Changes and Handling Failures	the module's treatment of unit-of-work: grouping changes and handling failures, used to make the module's main design claim concrete in design work, refactoring, and capstone evidence.