A3.9 · The roadmap layer · reference module
The reference module
The chapter's appendix: every key term to a one-line abstract, its Source, and a link to where the framework implements the idea — a course you can look up.
Where the teaching modules build the argument, this one indexes it. Three dives: the
glossary (the expandable list of terms), the annotated sources
(the bibliography with abstracts), and the idea→framework crosswalk (each idea
to the /elixir/phoenix chapter that runs it). Filter the index on the right
to see what it covers.
What the index covers · filter by category
The reference module
A3.9 is the chapter's — and the course's — appendix. The teaching modules build the
argument; this one indexes it. A glossary is a closed, data-driven list: a fixed set of terms where
each entry carries a term, a one-line abstract, its Source, and a link to the
/elixir/phoenix chapter where the framework implements the idea. It is the
place to look a concept up and jump to its real code — not the place to learn it for the first
time.
Closed means complete: no entry without a real abstract, a real Source, and a real, resolving framework link. That is what makes the reference module a tool rather than a summary. Every term resolves three ways — to a sentence that defines it, to a book that grounds it, and to a route you can open to see it built.
Which dive answers your question · pick an intent
A glossary is an index, not a tutorial — a fixed list of terms, each pointing outward to where it is defined and where it is used.
The index points at the real Portal: each term links to the
/elixir/phoenix chapter where the framework implements the idea, so a
concept resolves to code.
The reference module turns the course into something you can look up — every term to an abstract, a Source, and the line of the framework that makes it real.
The three dives
Read them in the arc look up → read deeper → open the code: the glossary to find a term, the sources to read the canon behind it, the crosswalk to jump to where the framework implements it. A3.9.1 starts.
The glossary
The full expandable accordion: fifteen key terms, each with its abstract, Source, and the /elixir chapter where the framework implements it. Degrades to a visible list without JS.
The annotated sources
The bibliography: every vetted Source with an abstract and the modules that cite it — one place to read deeper on any technique.
The idea→framework crosswalk
Each course idea mapped to the /elixir/phoenix chapter that implements it — the nine F6 rungs as routes you can open, all 200.
After A3.9, return to the A3 module navigation to continue the chapter, or follow a glossary link into the companion F6 Phoenix chapter to see an idea built.
References
The canon the reference module indexes, and where it connects in the course.
Sources
- Hunt & Thomas — The Pragmatic Programmer — tracer bullets, the single source of truth, design by contract.
- Beck, K. — Extreme Programming Explained — small batches and the inspect-and-adapt loop.
- Humble & Farley — Continuous Delivery — the roadmap as the delivery plan, releasable at every increment.
Related in this course
- A3.9.1 · The glossary — the expandable list.
- A3.9.2 · The annotated sources — the bibliography.
- A3.9.3 · The idea→framework crosswalk — idea to code.
- A3 · The roadmap layer — the chapter.
- A2 · Decomposition — the backlog the terms describe.
- A1 · Why an Agile Agent Workflow — the case the terms argue.
- F6 · The Portal on the web — where the framework implements the ideas.
- Companion · Functional Programming in Elixir — the framework course.