# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **The solver (R1).** Build what `R1. The solver` asks for, to the numbers in `design.md`. In particular: A fixed timestep of 1/60 s. The chosen resolution is a square grid. Check: the `R1. The solver` acceptance checks pass. 3. **A scripted stroke (R2).** Build what `R2. A scripted stroke` asks for, to the numbers in `design.md`. In particular: `fixtures/fluid-stroke.json` is a list of pointer samples (x, y, force, colour) at listed ticks. Check: the `R2. A scripted stroke` acceptance checks pass. 4. **Files (R3).** Build what `R3. Files` asks for, to the numbers in `design.md`. In particular: One command runs the field checks and the tapes, and writes the four screenshots including `clear`. No network. Tests may run the solver on the CPU if a GPU is missing, as long as the checksums match. Check: the `R3. Files` acceptance checks pass. 5. **Inputs (R4).** Build what `R4. Inputs` asks for, to the numbers in `design.md`. In particular: The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: the `R4. Inputs` acceptance checks pass. 6. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 7. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.