Pressure Routes¶

Page Maps¶

graph LR
  family["Reproducible Research"]
  program["Deep Dive Snakemake"]
  section["Guides"]
  page["Pressure Routes"]
  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"]

Read the first diagram as a timing map: this page is for non-ideal reading conditions, not calm full-course study. Read the second diagram as the loop: name the pressure, choose one bounded route, use one proof surface, then stop when the owning workflow boundary is visible.

Use this page when urgency is shaping what you can realistically read.

Choose the route that matches the pressure¶

Pressure	First page	First module or reference	First proof surface	Stop when you can name...
first contact	Start Here	Module 00, Module 01	Capstone Walkthrough	one truthful file contract and one reason the capstone is not first contact
inherited workflow repair	Anti-Pattern Atlas	Module 03, Module 04	Command Guide	whether the failure is workflow semantics, policy drift, interface sprawl, or execution context
publish and stewardship review	Course Guide	Module 06, Module 07, Module 10	Capstone Proof Guide	what downstream trust depends on and which route is strong enough to defend it
incident pressure	Capstone Review Worksheet	Module 09, Topic Boundaries	Capstone Proof Guide	the symptom, the owning workflow boundary, and the next smallest confirming command

What not to do under pressure¶

do not start with the whole capstone repository
do not escalate to the strongest proof route because the situation feels urgent
do not read governance pages before the current workflow boundary is named
do not open every support page when one route already matches the pressure

Good companion pages¶

Module Promise Map when the route needs a sharper module contract
Proof Ladder when the current command still feels too heavy
Capstone Map when you know the module but not the repository surface
Topic Boundaries when the pressure is really outside the course boundary

Good stopping point¶

Stop when you know which workflow boundary owns the current problem and which next page or command would test that claim directly. If you still cannot name the boundary, return to the table above instead of widening the reading surface.