Skip to content

Capstone Walkthrough

Guide Fit

flowchart TD
  family["Python Programming"] --> program["Python Functional Programming"]
  program --> pressure["A concrete learner or reviewer question"]
  pressure --> guide["Capstone Walkthrough"]
  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 you want the capstone as a guided learner story instead of as package reference alone.

  1. Read FuncPipe Capstone Guide.
  2. Run make PROGRAM=python-programming/python-functional-programming inspect if you need the quickest review map before running tests.
  3. Run make PROGRAM=python-programming/python-functional-programming capstone-walkthrough.
  4. Read Capstone Proof Guide if you want to compare the walkthrough with the stronger saved proof routes.
  5. Read the generated pytest.txt, focus-areas.txt, package-tree.txt, and test-tree.txt in that order.
  6. Run make PROGRAM=python-programming/python-functional-programming capstone-tour only when you want the learner-facing proof bundle after the walkthrough is already clear.
  7. Run make PROGRAM=python-programming/python-functional-programming capstone-verify-report when you need a saved review bundle with the executed test record.
  8. Compare what you learned with Capstone Architecture Guide, Capstone Test Guide, and Capstone Review Worksheet.

What the walkthrough should teach

  • how the proof bundle mirrors the course sequence
  • how the test surface makes the code promises visible first
  • how package layout reveals where purity, composition, and effects live
  • how the project contract and guide pages keep the capstone readable to a human reviewer