Return Map¶

Concept Position¶

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

flowchart LR
  pause["Return after a break"] --> promise["Re-anchor the course promise and arc"]
  promise --> boundary["Choose the last stable boundary you still trust"]
  boundary --> guide["Open the matching guide and capstone route"]
  guide --> proof["Run one small proof route"]
  proof --> resume["Resume with context restored instead of guessed"]

Use this page when the course is familiar but no longer fresh. The goal is not to reread everything. The goal is to restart from the last stable design boundary instead of from the most advanced module title that still looks recognizable.

Step 1: Re-anchor the course shape¶

Before you reopen a content module, reread:

That restores the course arc, the promise of each module, and the pressure-based route before details start competing again.

Step 2: Re-enter from the last boundary you still trust¶

Use the last module range you can still explain clearly 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 Matrix, Capstone Map
Modules 04 to 06	Module 07 and Engineering Question Map	Boundary Review Prompts, Review Checklist
Modules 07 to 08	Module 09 and Mastery Map	Outcomes and Proof Map, FuncPipe Capstone Guide
Module 09 or later	Module 10 and the capstone proof routes	Self-Review Prompts, Proof Matrix

Step 3: Use one proof route before resuming¶

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

make PROGRAM=python-programming/python-functional-programming capstone-test when you need executable confidence quickly
make PROGRAM=python-programming/python-functional-programming capstone-tour when you need the human walkthrough route
make PROGRAM=python-programming/python-functional-programming capstone-verify-report when you need saved executable proof

The proof route should restore your bearings, not replace the module.

Signals you returned too far ahead¶

Move backward one boundary if you cannot answer:

where purity still ends and orchestration begins
which capstone package or test file proves the claim you are trying to recover
which course arc owns the current pressure

If those answers are fuzzy, the issue is probably not missing vocabulary. It is that the last stable boundary was earlier than you first assumed.