# Math motion ## What this builds A short, original math animation: equations and shapes that move, written as a scene graph, rendered in the browser or in Python. Fixture scenes have a documented frame count. Golden frames are taken at stated times, and the positions of a couple of text or shape elements are asserted. This is a moving argument, not a slide deck, and it is not a copy of a famous channel's typography or name. Read `spekkr.inputs.json` first. `title` is on the opening card. `fps` and `hold` size the timeline. `labels` and `subtitle` change the chrome. `renderer` is the engine. ## Out of scope - A general computer-algebra system, or a full course platform. - A trademarked channel's typography or name. - A live classroom service in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Timeline and positions - 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. - At the listed times, named elements (for example the left-hand side of an equation, or a plotted point) have positions in `fixtures/math-keys.json`, within 1 px or 0.5% of the frame, as the file says. - Two renders of the same scene hash the same frames, or match within a 2-level pixel tolerance if the two renderers differ slightly, as documented. Accept when: the frame count is exact, the key positions match, and a same-renderer pair of runs hashes equal. ### R2. Goldens and files - Goldens at the title card, a mid-transform, a settled equation, and the last frame, at the times in the file. - One command renders, counts, asserts positions, and writes the frames. No network. Accept when: the command passes for both renderers (with the documented inter-renderer tolerance), and a deliberately short hold fails the frame count. ### R3. Inputs - Inputs are read from `spekkr.inputs.json`. `fps`, `hold` or `frames` and the frame size stay inside the ranges in `design.md`. - A value outside a range is refused before a render. Accept when: an illegal input is refused by name, and the default timeline has the frame count in `design.md`. ### R4. Checks and report - One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. - Checks do not need a network, a paid API, or physical hardware. Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it. ## Verification Fixture scenes render to a documented frame count. Golden frames are taken at stated times, and text or shape positions at a couple of keyframes are asserted. Two runs of the same renderer agree. No network is required. The product does not use a famous channel's name. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to render a scene, how the timeline is listed, and how to add a key position.