Skip to content

Capstone Proof Checklist

Guide Fit

flowchart TD
  family["Reproducible Research"] --> program["Deep Dive Make"]
  program --> pressure["A concrete learner or reviewer question"]
  pressure --> guide["Capstone Proof Checklist"]
  guide --> next["Modules, capstone, and reference surfaces"]
flowchart TD
  question["Do you need one full proof pass?"] --> route["Run the bounded proof route"]
  route --> inspect["Inspect the saved evidence in order"]
  inspect --> judgment["Leave with one explicit judgment about trust"]

Read the first diagram as a timing map: this checklist is for one end-to-end proof pass, not for first contact. Read the second diagram as the rule: run the bounded proof route, inspect the evidence in order, then leave with one explicit judgment about trust.

Use this checklist after Module 03, or later when you need a steward-level review route before incident, profile, or migration questions.

Bounded proof pass

  1. Run make PROGRAM=reproducible-research/deep-dive-make proof.
  2. Read Command Guide.
  3. Read capstone/Makefile and capstone/tests/run.sh.
  4. Inspect artifacts/proof/reproducible-research/deep-dive-make/selftest/.
  5. Inspect artifacts/audit/reproducible-research/deep-dive-make/contract/.
  6. Inspect artifacts/audit/reproducible-research/deep-dive-make/incident/.
  7. Inspect artifacts/audit/reproducible-research/deep-dive-make/profile/.
  8. If you still need failure-class study after the bounded proof route, step down into programs/reproducible-research/deep-dive-make/capstone/ and run gmake repro.

Questions this proof pass should answer

  • what selftest proves that all does not
  • where the public contract becomes inspectable
  • where hidden inputs and generated boundaries are made visible
  • which saved bundle would matter most to another maintainer
  • which repro teaches a real failure class instead of a toy surprise

Good stopping point

Stop when you can write one explicit judgment in your own words:

  • trust the build contract as-is
  • trust it with one named boundary to revisit
  • do not trust it yet because one specific proof surface is still missing

If you cannot make one of those judgments, repeat the bounded route before adding more commands.

Best follow-up routes