Skip to content

Capstone Proof Guide

Guide Fit

flowchart TD
  family["Python Programming"] --> program["Python Functional Programming"]
  program --> pressure["A concrete learner or reviewer question"]
  pressure --> guide["Capstone Proof Guide"]
  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 a lesson makes a design claim and you want the most direct evidence in the capstone.

Proof route

  1. Read FuncPipe Capstone Guide.
  2. Run make PROGRAM=python-programming/python-functional-programming inspect when you need the fastest inventory of package, test, and guide ownership.
  3. Run make PROGRAM=python-programming/python-functional-programming test for direct executable verification.
  4. Run make PROGRAM=python-programming/python-functional-programming capstone-walkthrough when you need the guided learner-facing walkthrough before escalating proof.
  5. Run make PROGRAM=python-programming/python-functional-programming capstone-verify-report when you want a review bundle with the executed test record.
  6. Run make PROGRAM=python-programming/python-functional-programming capstone-tour for the learner-facing proof bundle.
  7. Run make PROGRAM=python-programming/python-functional-programming proof when you want the sanctioned end-to-end route.
  8. Run make PROGRAM=python-programming/python-functional-programming capstone-confirm when you want the strictest confirmation route exposed by the catalog.
  9. Use Capstone Review Worksheet to decide whether the evidence is strong enough.

What you should be able to answer after proof review

  • Which package owns the checked behavior?
  • Which test or artifact confirmed it?
  • Which future change would require stronger or different proof?