Skip to content

Design Question Map

Guide Fit

flowchart TD
  family["Python Programming"] --> program["Python Metaprogramming"]
  program --> pressure["A concrete learner or reviewer question"]
  pressure --> guide["Design Question Map"]
  guide --> next["Modules, capstone, and reference surfaces"]
flowchart TD
  question["Name the exact question you need answered"] --> skim["Skim only the sections that match that pressure"]
  skim --> crosscheck["Open the linked module, proof surface, or capstone route"]
  crosscheck --> next_move["Leave with one next decision, page, or command"]

Read the first diagram as a timing map: this guide is for a named pressure, not for wandering the whole course-book. Read the second diagram as the guide loop: arrive with a concrete question, use only the matching sections, then leave with one smaller and more honest next move.

Use this page when the learner problem is easier to name than the module or mechanism that teaches it.

Use this map well

  • Start from the engineering question, not from the mechanism you think might answer it.
  • Choose one row first, not several at once.
  • Leave the page once one module range and one capstone cross-check are clear.

Question to route table

If the question is... Start with Keep this guide open Capstone cross-check
What is Python actually doing at runtime here? Modules 01 to 03 First-Contact Map manifest output and framework.py
How can I inspect this safely without accidentally running business logic? Module 02 Proof Ladder make manifest, make registry, and cli.py
Did this wrapper preserve the callable contract honestly? Modules 03 to 05 Mechanism Selection make action, make signatures, and actions.py
Should this behavior live in a wrapper, a property, or a descriptor? Modules 06 to 08 Mechanism Selection fields.py, make field, and field tests
Does this rule truly belong at class creation time? Module 09 Mastery Map make registry, framework.py, and registry tests
Is this metaclass doing real work or just hiding a lower-power option? Module 09 Anti-Pattern Atlas registry output and constructor signatures
Which runtime hooks are too dangerous to approve casually? Module 10 Review Checklist make verify-report and the saved public evidence
What would I reject as making the system more magical than necessary? Module 10 Topic Boundaries capstone proof bundle and review worksheet

How to use it well

  1. Name the design question in one sentence.
  2. Start with the smallest module range that answers that question.
  3. Keep one guide open so the route and exit bar stay visible.
  4. Use the capstone only after you can say what you are trying to confirm.

Good stopping point

Stop with this map once you can say:

  • which exact question you are trying to answer
  • which module range owns that answer
  • which capstone surface is the first honest cross-check

Good companion pages