# Data shader ## What this builds A scene whose look is a shader, driven by a small set of uniforms from a time series: wind, brightness, a pulse. The series is a fixture file, not a live market or weather feed. Tests map fixture values to documented uniforms and take golden frames for a calm series and a chaotic one. A hook fails if a live feed host is contacted. Read `spekkr.inputs.json` first. `title` is in a corner. `series` chooses a fixture. `look` is the scene. `labels` and `play` change the chrome. Tests pin an instant in the series. ## Out of scope - A live market, weather, or sensor feed in the checks. - A paid data API in the checks. - A trading claim. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Uniforms - Each instant in `fixtures/series-calm.json` and `fixtures/series-chaotic.json` maps to uniforms listed in `fixtures/shader-uniforms.json`, within 1e-4. - A pinned instant (calm at t = 12 s, chaotic at t = 12 s) is used for the goldens. - A fetch hook fails if a known market or weather host is contacted. Accept when: every listed instant's uniforms match, and the hook stays quiet. ### R2. Frames and files - Goldens: calm, chaotic, a readout of the calm instant, and a frozen (play off) calm view, which should match calm. - One command maps the series, hooks, and writes the frames. No network. Accept when: the command passes for both looks (sibling goldens), and the frames match. ### R3. Inputs - 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. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ### 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 time-series values map to documented shader uniforms, within 1e-4. Golden frames cover calm and chaotic inputs. A fetch hook fails if a live market or weather feed is contacted. No paid API and no network are required. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to add a series, how uniforms are named, and how to run the checks.