# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Install the simulator or the HDL toolchain named in `design.md` (ngspice, Icarus, Verilator, or a KiCad/SVG board tool). Read the inputs into one place. Check: a trivial netlist or testbench runs and writes a file. 2. **The loop (R1).** Build what `R1. The loop` asks for, to the numbers in `design.md`. In particular: The testbench dumps `frames` frames of a complete turn. Frame 0, a quarter turn, and a half turn match goldens, exact or within the file's tolerance. Check: the `R1. The loop` acceptance checks pass. 3. **Cap and files (R2).** Build what `R2. Cap and files` asks for, to the numbers in `design.md`. In particular: A documented count script reports a figure at or under the bound in `design.md` (a tiny-ASIC-like budget, for example a 4k-gate or a one-tile bound, as the file states). Check: the `R2. Cap 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`. Values outside the ranges or choices in `design.md` are refused before a netlist, a board or a testbench is built. 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 the simulation or the testbench, writes the plots or dumps, and compares them to the numbers in `design.md`. Check: the `R4. Checks and report` acceptance checks pass. 6. **Plots, dumps and goldens.** Write the plots or framebuffer dumps named in `design.md` and compare them to the tables there. Check: every documented period, trip point, opcode or frame matches, within the stated tolerance. 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.