Proof Matrix¶

Page Maps¶

graph LR
  family["Reproducible Research"]
  program["Deep Dive Make"]
  section["Guides"]
  page["Proof Matrix"]
  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.

This page maps the course's main claims to the commands and files that prove them.

Use it when you know what concept you care about but want the fastest evidence route.

Core Build Claims¶

Start with the repository-root commands below. Step down into programs/reproducible-research/deep-dive-make/capstone/ only when a row names the raw reference build directly.

Claim	Command	File surfaces
the capstone has a bounded first-pass reading route	`make PROGRAM=reproducible-research/deep-dive-make capstone-walkthrough`	`course-book/capstone/index.md`, `artifacts/walkthrough/reproducible-research/deep-dive-make/`
the graph converges after a successful build	`make PROGRAM=reproducible-research/deep-dive-make test`	`capstone/Makefile`, `capstone/tests/run.sh`
parallelism does not change artifact meaning	`make PROGRAM=reproducible-research/deep-dive-make test`	`capstone/tests/run.sh`, `capstone/repro/`
discovery is deterministic	`make PROGRAM=reproducible-research/deep-dive-make capstone-discovery-audit`	`capstone/mk/objects.mk`
hidden inputs are modeled explicitly	`gmake -C capstone --trace all`	`capstone/mk/stamps.mk`
generated files are treated as graph nodes	`gmake -C capstone --trace dyn`	`capstone/Makefile`, `capstone/scripts/gen_dynamic_h.py`

Operational Claims¶

Claim	Command	File surfaces
the build has a stable public API	`make PROGRAM=reproducible-research/deep-dive-make help`	`capstone/Makefile`
the layered `mk/*.mk` structure has explicit responsibilities	inspect `capstone-architecture-guide.md`	`capstone/mk/*.mk`
artifact boundaries are smaller than the whole repository	inspect `capstone-review-worksheet.md`	`capstone/build/`, `capstone/repro/`, `capstone/tests/`
the build can explain rebuild behavior	`gmake -C capstone --trace all`	`capstone/Makefile`, `capstone/mk/*.mk`
the build declares portability boundaries	`make PROGRAM=reproducible-research/deep-dive-make capstone-portability-audit`	`capstone/mk/contract.mk`
the build produces non-contaminating evidence	`gmake -C capstone attest`	`capstone/Makefile`, `build/attest.txt`
the repro pack teaches real failure classes	`gmake -C capstone repro`	`capstone/repro/`, `course-book/capstone/capstone-proof-guide.md`

Review Claims¶

Question	Best first command	Best first file
where should the first capstone pass start	`make PROGRAM=reproducible-research/deep-dive-make capstone-walkthrough`	`course-book/capstone/index.md`
why did this rebuild	`gmake -C capstone --trace all`	`capstone/mk/stamps.mk`
why is `-j` unsafe	`make PROGRAM=reproducible-research/deep-dive-make test`	`capstone/repro/01-shared-log.mk`
where is the build API	`make PROGRAM=reproducible-research/deep-dive-make help`	`capstone/Makefile`
how is code generation modeled	`gmake -C capstone --trace dyn`	`capstone/scripts/gen_dynamic_h.py`
what would I review before migration	`gmake -C capstone -p > build/review.dump`	`capstone/mk/`

Companion Pages¶

The most useful companion pages for this matrix are: