Reference¶

Page Maps¶

graph LR
  family["Reproducible Research"]
  program["Deep Dive Snakemake"]
  section["Reference"]
  page["Reference"]
  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 shelf is for durable Snakemake vocabulary, boundary questions, and completion standards. Use it when the workflow concept is already recognizable and you need a stable review surface for contracts, dynamic discovery, operating policy, or publish trust.

Choose the right reference route¶

If your question is...	Best page
What does this term mean locally?	Glossary
Where does this idea sit in the course sequence?	Module Dependency Map
What should I practice or prove next?	Practice Map
How should I review this workflow claim?	Review Checklist
Which sharper boundary question should I ask?	Boundary Review Prompts
How can I turn this idea into active recall?	Self-Review Prompts
What workflow failure shape am I seeing?	Anti-Pattern Atlas
What counts as genuinely complete understanding?	Completion Rubric
Does this question belong in the course center or at its edge?	Topic Boundaries

What this shelf is for¶

keeping workflow contracts, discovery evidence, policy, and publish language stable
turning workflow review into explicit keep, change, or reject calls
connecting module order to local proof loops and capstone follow-up
deciding whether a workflow claim is backed by the right contract or evidence surface

Guide set¶

Stop here when¶

you know which workflow boundary owns the current question
you can turn that page into one explicit trust judgment
you know whether the next move is back to a module or into the capstone