Return Map¶

Concept Position¶

flowchart TD
  family["Python Programming"] --> program["Python Metaprogramming"]
  program --> module["Module 00: Orientation and Study Practice"]
  module --> concept["Return Map"]
  concept --> capstone["Capstone pressure point"]

flowchart TD
  pause["Return after time away"] --> orient["Re-anchor the course promise and ladder"]
  orient --> checkpoint["Choose the last stable module boundary"]
  checkpoint --> support["Open the matching support pages"]
  support --> capstone["Use one small capstone proof route"]
  capstone --> resume["Resume the next module with context restored"]

Read the first diagram as a placement map: this page is one concept inside its parent module, not a detached essay, and the capstone is the pressure test for whether the idea holds. Read the second diagram as the working rhythm for the page: re-anchor the course promise, find the last stable boundary you remember clearly, and use one small proof step before resuming the next module.

Use this map when the course is not new, but no longer feels fresh. The goal is not to reread everything. The goal is to restart from the smallest honest boundary instead of guessing where your understanding is still solid.

Step 1: Re-anchor the course promise¶

Before you reopen the last module you touched, reread:

That puts the power ladder and the module promises back in view before details compete for attention again.

Step 2: Choose the last boundary you still trust¶

Use the last module you can still explain without rereading as your re-entry boundary.

If you still trust yourself through...	Re-enter with...	Keep open...
Modules 01 to 03	Mid-Course Map and Module 04	Proof Ladder, Capstone Map
Modules 04 to 06	Module 07 and Mechanism Selection	Module Checkpoints, Anti-Pattern Atlas
Modules 07 to 08	Module 09 and Mastery Map	Review Checklist, Outcomes and Proof Map
Module 09 or later	Module 10 and the capstone proof routes	Boundary Review Prompts, Capstone Guide

Step 3: Use one proof route before resuming¶

Pick one small proof route that matches the boundary you are returning to:

make manifest or make registry if you are refreshing observation and definition-time visibility
make action or make trace if you are refreshing wrapper behavior
make field if you are refreshing descriptor ownership
make verify-report if you are refreshing review judgment and governance boundaries

The proof route should restore confidence, not become a full audit.

Signs you re-entered too late¶

Move backward one boundary if you cannot answer:

what lower-power alternative is still relevant here
what capstone file or output proves the module claim
what kind of runtime timing is under discussion

If any of those feel fuzzy, the problem is probably not memory for terms. It is that the last stable boundary was earlier than you thought.