Practice Map

Page Maps

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

Use this page when you want to know what kind of local exercise and proof fits each module before you widen into the capstone.

Module practice surfaces

Module	Primary practice surface	Main proof loop	Best capstone follow-up
01	object-model inspection exercises	explain one runtime fact without changing behavior	inspect manifest and registry outputs
02	inspection and introspection labs	compare what different inspection tools can observe honestly	inspect public runtime evidence before touching wrappers
03	signature and provenance exercises	preserve metadata while adding evidence	inspect callable surfaces and saved outputs
04	thin-wrapper refactors	wrap one function while keeping names, docs, and blame legible	inspect action wrappers and tests
05	decorator-policy exercises	compare policy-in-decorator versus explicit composition	inspect decorator seams and review routes
06	class-customization labs	solve a class problem without escalating to metaclasses yet	inspect framework edges before class-creation hooks
07	descriptor exercises	give one attribute rule an explicit owner and prove lookup behavior	inspect field descriptors and focused tests
08	descriptor-system design labs	compare one descriptor to a reusable descriptor framework	inspect validation and generated constructor behavior
09	metaclass escalation reviews	write down the lower-power tool that almost worked before using a metaclass	inspect registration and class-creation routes
10	runtime governance review	justify one mechanism choice against the whole power ladder	use the capstone as the final review specimen

Reusable proof loops

• observation loop: inspect shape first, then explain what changed, then decide whether transformation was necessary
• escalation loop: name the lowest honest tool, the invariant it could not own, and the new risk introduced by a stronger one
• governance loop: explain what a reviewer should still be able to understand one file at a time