Reference¶
Reference Position¶
flowchart TD
family["Reproducible Research"] --> program["Deep Dive DVC"]
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 DVC. These pages are for questions that recur across modules: state authority, evidence boundaries, learning order, comparison routes, and course completion standards.
Use This Section When¶
- you need the right vocabulary before reading a module again
- you want to know which state layer settles a trust question
- you need the right proof route rather than the strongest one
- you are reviewing whether the course promise is being met
Reference Pages¶
- Module Dependency Map for concept order and prerequisite shape
- Authority Map for deciding which layer is authoritative
- Evidence Boundary Guide for separating declaration, execution, promotion, and recovery proof
- Glossary for durable language
- Version Support Guide for the supported toolchain contract and the commands that prove you are still inside it
- Topic Boundaries for what the course treats as core, supporting, and boundary material
- Practice Map for module-to-proof routing
- Anti-Pattern Atlas for routing common reproducibility smells to the right repair path
- Verification Route Guide for picking the right command
- Completion Rubric for course and repository review
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.