Deep Dive Make Capstone Guide¶

Page Maps¶

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

This capstone is the executable reference build for Deep Dive Make. It keeps graph truth, atomic publication, parallel safety, determinism, and self-testing in one compact repository so the course can point to real evidence instead of slogans.

Use this guide once the local module idea is already legible. The capstone should answer one build question at a time, not become a full repository tour by default.

What this capstone proves¶

public targets can stay small and stable
graph truth can survive hidden-input and generated-file pressure
serial and parallel execution can agree when the build deserves trust
failure specimens can stay isolated and teachable without polluting the healthy build

Choose the right capstone route¶

If your question is...	Best page
Which capstone surface matches the current module?	Capstone Map
Which targets or commands are public?	Command Guide
Which files own the build behavior?	Capstone File Guide
Where do contract, graph, proof, and repro ownership live?	Capstone Architecture Guide
Which proof route is honest for this claim?	Capstone Proof Guide
How should I review the repository as a steward?	Capstone Review Worksheet
Where should a new change land?	Capstone Extension Guide

Start by module range¶

Module range	Best capstone focus
Modules 01-02	truthful edges, atomic publication, and one explainable race condition
Modules 03-05	selftests, public targets, portability, and hidden-input proof
Modules 06-08	generator boundaries, layered `mk/` design, and release surfaces
Modules 09-10	incident review, stewardship judgment, and extension pressure

Core commands¶

If you need...	From the repository root	From the capstone directory
the first bounded pass	`make PROGRAM=reproducible-research/deep-dive-make capstone-walkthrough`	`gmake walkthrough`
public-contract review	`make PROGRAM=reproducible-research/deep-dive-make inspect`	`gmake inspect`
the steward-level proof route	`make PROGRAM=reproducible-research/deep-dive-make proof`	`gmake proof`

On macOS, use gmake inside capstone/ because /usr/bin/make is BSD Make.

Guide set¶

Review questions¶

Which targets are truly public, and which are only helper surfaces?
Which file proves convergence and parallel safety instead of merely claiming them?
Which failure class is the healthy build defending against right now?

Stop here when¶

you know the current build claim in plain language
you know the smallest file, guide, or command that can prove it
you know whether a wider steward review is actually necessary