# 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. **State (R1).** Build what `R1. State` asks for, to the numbers in `design.md`. In particular: State is counts of three organisms (`grazer`, `bloom`, `filter`) and four chemistry values in [0, 1]: light, food, waste, oxygen. Check: the `R1. State` acceptance checks pass. 3. **Tending (R2).** Build what `R2. Tending` asks for, to the numbers in `design.md`. In particular: A `feed` adds 0.3 food, clamped to 1. A `light` input sets light to a value in [0, 1]. Check: the `R2. Tending` acceptance checks pass. 4. **Frames and files (R3).** Build what `R3. Frames and files` asks for, to the numbers in `design.md`. In particular: Goldens: calm at tick 0, after the feed tape, crowded at tick 0, and a chemistry-meters close-up of calm at 48. Check: the `R3. Frames and 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.