Skip to content

Capstone Walkthrough

Page Maps

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

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 study 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 guided 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 Proof 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