First-Contact Map¶
Page Maps¶
graph LR
family["Reproducible Research"]
program["Deep Dive Make"]
section["Orientation"]
page["First-Contact Map"]
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"]
Use this page for your first honest session with the course. The goal is not to cover as much ground as possible. The goal is to leave the first hour coherent enough that later reading choices feel deliberate instead of random.
First session route¶
- Read
../index.mdfor the program promise. - Read
index.mdfor the Module 00 role. - Read
course-map.mdto see the four course arcs. - Read
../guides/start-here.mdwhen you want the shortest starting route. - Read
../capstone/capstone-map.mdonly if a repository specimen will clarify, not blur, the current idea. - Run one bounded command:
What you should know before Module 01¶
Before the first technical module, you should be able to answer:
- what this course treats as the core promises of a good build system
- why the capstone is an executable corroboration surface rather than the first thing to read
- which course arc matches your current pressure: graph truth, discipline, system design, or stewardship
First-week rhythm¶
Repeat the same rhythm through the first modules:
- read until the current build question is clear
- inspect one matching example, exercise, or capstone surface immediately
- run one bounded command instead of escalating to every proof route
- stop when you can state one rule and one failure mode in plain language
When to leave this route¶
Move to mid-course-map.md once Modules 01 to 03 feel stable and the main question becomes semantics under pressure, hardening, release trust, or incidents.