# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Add the tables in `design.md`, a clock that tests can set, the adapter interface and a stand-in service. If there is no server yet, build the smallest one: users who can sign in from a phone. Check: migrations run from empty. 2. **Phones (R1).** Check: the R1 acceptance tests pass. 3. **Send (R2).** The list of types, `push`, and the cut that keeps a payload under its size. Check: the R2 acceptance tests pass. 4. **Quiet hours (R6).** Only if `quiet_hours` is on. A pure function from a time, a time zone, `quiet_start` and `quiet_end` to when to send. Check: a test covers every row of the table of cases in `design.md`. 5. **The worker, retries and dead tokens (R4, R5).** Against the stand-in. Check: the R4 and R5 acceptance tests pass. 6. **The real adapters (R3).** For the `targets` input. Check: each row of the table of answers in `design.md` has a test, and the sign-in is reused. 7. **Preferences (R7) and badges (R8).** R8 only if `badge_counts` is on. Check: the R7 and R8 acceptance tests pass. 8. **A record (R9).** Check: the R9 acceptance tests pass. 9. **Finish.** Write the README and run the whole test suite. Check: every item under "Definition of done" in `spec.md` is true.