Pressure Routes¶
Guide Fit¶
flowchart TD
family["Reproducible Research"] --> program["Deep Dive Make"]
program --> pressure["A concrete learner or reviewer question"]
pressure --> guide["Pressure Routes"]
guide --> next["Modules, capstone, and reference surfaces"]
flowchart TD
question["Name the pressure honestly"] --> route["Choose one bounded route"]
route --> proof["Use one matching proof surface"]
proof --> next_move["Stop when the owning boundary is visible"]
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 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 edge and one reason the capstone is not first contact |
| inherited build repair | Anti-Pattern Atlas | Module 04, Module 05 | Command Guide | whether the failure is graph truth, publication, portability, or a hidden input |
| release and stewardship | Course Guide | Module 07, Module 08, Module 10 | Capstone Proof Checklist | the public contract, the proof bar, and the extension boundary |
| incident pressure | Incident Ladder | Module 09 | Capstone Review Worksheet | the symptom, the owning 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 heaviest proof route because you feel urgency
- do not read governance pages before the current failure class is named
- do not open every guide 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 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.