# 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 API to put this in front of if there is none: one `POST` route with a counter and a caller taken from a header. Check: an empty test run passes. 2. **The fingerprint (R2).** A pure function. Check: a test reproduces both rows of the table in `design.md`. 3. **The store.** The fields in `design.md` for the `store` input, with the one step that records a key. Check: of 20 attempts at once to record one key, one succeeds. 4. **The header (R1) and the first request (R2).** Check: the R1 and R2 acceptance tests pass. 5. **Again (R3), for something else (R4), two at once (R5).** Check: the R3, R4 and R5 acceptance tests pass. 6. **What is kept (R6) and forgetting (R7).** Use the `key_hours` input. Check: the R6 and R7 acceptance tests pass. 7. **Keys required (R8).** Only if `require_key` is on. Check: the R8 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.