You already know: every mechanism this list describes, from the lessons of this domain. This lesson is the map back to the sources.
Why this matters for Atlas. Engines change every few months; the ideas underneath them change slowly. A staff engineer reads a new serving paper by asking which bottleneck it attacks, what single mechanism removes it, what the headline number was measured against, and where it does not help. This lesson gives that method and then a short, annotated list of the papers that built modern LLM serving, each tied to the lesson that teaches it. The numbers quoted are the papers' own reported results on their workloads, not guarantees for yours.
How to use this list. Read each paper's abstract, introduction and evaluation set-up first; reproduce one number with the lesson's code; only then read the method in full.
1. How to read a systems paper
The question. A new paper claims "3× higher throughput". What do you check before believing it applies to you?
Start from nothing. Five questions, in order: