# 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 craft (R1).** Build what `R1. The craft` asks for, to the numbers in `design.md`. In particular: The lander is a 4 m tall, 2 m wide rectangle. Dry mass 200 kg plus `fuel`. Thrust is 800 N downward and 200 N sideways, burning 0.6 kg/s when a downward thruster is on and 0.15 kg/s when a side thruster is on. Check: the `R1. The craft` acceptance checks pass. 3. **The field (R2).** Build what `R2. The field` asks for, to the numbers in `design.md`. In particular: The fluid is a 128 by 96 staggered grid over a 64 by 48 m world. Density and velocity are stored. The chosen solver steps the field each tick. Check: the `R2. The field` acceptance checks pass. 4. **Landing and crash fixtures (R3).** Build what `R3. Landing and crash fixtures` asks for, to the numbers in `design.md`. In particular: `fixtures/lander-soft.json` is a control tape that, from the documented start, produces a soft landing on pad A at t = 8.0 s, with the pose in the file. Check: the `R3. Landing and crash fixtures` acceptance checks pass. 5. **Frames and files (R4).** Build what `R4. Frames and files` asks for, to the numbers in `design.md`. In particular: Four frames: approach at t = 2 s of the soft tape, plume-on at t = 4 s, soft-landing at contact, crash at contact of the crash tape. Check: the `R4. Frames and files` acceptance checks pass. 6. **Inputs (R5).** Build what `R5. 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 `R5. Inputs` acceptance checks pass. 7. **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. 8. **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.