# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** A test runner, a clock that tests can set, and the smallest app to put the limiter in front of if there is none: one route and a health check. Check: an empty test run passes. 2. **The algorithm (R1).** A pure function from the stored number, `now`, the limit and the window to a result, with no store at all. Check: a test walks the table of cases in `design.md` and every row matches. 3. **The store (R5, R8).** The interface in `design.md` for the `store` input. Check: the R5 test with 50 requests at once passes, and the R8 test passes. 4. **The caller (R2).** Check: the R2 acceptance tests pass. 5. **The answer (R3).** Status 429, `Retry-After`, and the three headers if `response_headers` is on. Use `default_limit` and `default_window_seconds`. Check: the R3 acceptance tests pass. 6. **Named limits (R4).** Only if `per_route_limits` is on. Check: the R4 acceptance tests pass. 7. **Store failures (R6) and exemptions (R7).** Check: the R6 and R7 acceptance tests pass. 8. **Finish.** Write the README and run the whole test suite. Check: every item under "Definition of done" in `spec.md` is true.