# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up the renderer in the `renderer` input. Read the inputs and the timeline or camera file into one place. Check: a single blank or title frame renders at the stated size. 2. **Timeline and positions (R1).** Build what `R1. Timeline and positions` asks for, to the numbers in `design.md`. In particular: The fixture scene in `design.md` has a frame count of `fps` times the duration in the file (including holds), exact as a whole number of frames. Check: the `R1. Timeline and positions` acceptance checks pass. 3. **Goldens and files (R2).** Build what `R2. Goldens and files` asks for, to the numbers in `design.md`. In particular: Goldens at the title card, a mid-transform, a settled equation, and the last frame, at the times in the file. Check: the `R2. Goldens and files` acceptance checks pass. 4. **Inputs (R3).** Build what `R3. Inputs` asks for, to the numbers in `design.md`. In particular: Inputs are read from `spekkr.inputs.json`. `fps`, `hold` or `frames` and the frame size stay inside the ranges in `design.md`. Check: the `R3. Inputs` acceptance checks pass. 5. **Checks and report (R4).** Build what `R4. Checks and report` asks for, to the numbers in `design.md`. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the `R4. Checks and report` 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.