Skip to content

Capstone Extension Guide

Page Maps

graph LR
  family["Python Programming"]
  program["Python Functional Programming"]
  section["Capstone"]
  page["Capstone Extension Guide"]
  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 the course asks not only "what is this boundary?" but also "where should the next change land?"

  1. Read Capstone File Guide.
  2. Compare the change you are imagining with Capstone File Guide.
  3. Use Capstone Review Worksheet to decide what proof must change with the implementation.

What a good answer looks like

  • you can name the owning package before editing code
  • you can explain why another nearby package should not absorb the change
  • you can name the proof surface that must evolve with the implementation