Skip to content

Reference

Reference Position

flowchart TD
  family["Reproducible Research"] --> program["Deep Dive Make"]
  program --> reference["Reference"]
  reference --> review["Design or review decision"]
  review --> capstone["Capstone proof surface"]
flowchart TD
  trigger["Hit a naming, boundary, or trade-off question"] --> lookup["Use this page as a glossary, map, rubric, or atlas"]
  lookup --> compare["Compare the current code or workflow against the boundary"]
  compare --> decision["Turn the comparison into a keep, change, or reject call"]

Read the first diagram as a lookup map: this page is part of the review shelf, not a first-read narrative. Read the second diagram as the reference rhythm: arrive with a concrete ambiguity, compare the current work against the boundary on the page, then turn that comparison into a decision.

The reference surface holds the durable reading aids for Deep Dive Make. These pages are for questions that recur across modules: vocabulary, learning order, stable target surfaces, build layers, artifact boundaries, incident debugging order, and review standards.

Use This Section When

  • you need the right vocabulary before reading a module again
  • you want to know which target or layer is public and which is implementation detail
  • you need the right proof route instead of the strongest one
  • you are reviewing whether the course and capstone are keeping their promises

Reference Pages

Directory glossary

Use Glossary when you want the recurring language in this shelf kept stable while you move between standards, checklists, prompts, and boundary calls.