Reference¶

Page Maps¶

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

This shelf is for durable functional-programming vocabulary, review questions, and completion standards. Use it when the module idea is already recognizable and you need a stable reference surface for design or review.

Choose the right reference route¶

If your question is...	Best page
What does this term mean locally?	Glossary
Where does this idea sit in the course sequence?	Module Dependency Map
What should I practice or prove next?	Practice Map
How should I review this design?	Review Checklist
Which sharper boundary question should I ask?	Boundary Review Prompts
How can I turn this idea into active recall?	Self-Review Prompts
What failure shape am I seeing?	Anti-Pattern Atlas
What counts as genuinely complete understanding?	Completion Rubric
Does this question even belong in the course center?	Topic Boundaries

What this shelf is for¶

keeping purity, failure modelling, and effect boundaries described with stable language
turning review into explicit keep, change, or reject calls
connecting module order to practice surfaces and capstone follow-up
deciding whether a claimed functional design actually deserves trust

Guide set¶

Stop here when¶

you know which reference page answers the current design or review question
you can turn that page into one explicit judgment
you know whether the next move is back to a module or into the capstone