Reference

Reference Position

flowchart TD
  family["Reproducible Research"] --> program["Deep Dive Snakemake"]
  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.

Use this page when you already know the course flow and need a stable reference surface instead of a learner-entry guide.

---

Vocabulary And Concepts

• Glossary
• Topic Boundaries

Back to top

---

Study And Proof Routing

• Module Dependency Map
• Practice Map
• Anti-Pattern Atlas

Back to top

---

Boundary And Repository Review

• Boundary Map
• Repository Layer Guide

Back to top

---

Completion And Stewardship

• Completion Rubric

Back to top

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.