# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Integration Timestep 1/60 s. Gravity 0.0 (the breeze is the force). Wind is a vector field from a small curl of value noise, seed 3, amplitude in `fixtures/ribbon-wind.json`. Constraint iterations: 8. ## Screenshot tolerance 8 levels, 98% of pixels, camera fixed as in the fixture. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A ribbon in a breeze | Shown in a corner. | | `strips` | Number of strips | 8 | From 1 to 24. | | `seed` | Breeze seed | 3 | A whole number. | | `collide` | Strip collisions | off | If on, strips push apart. The default is they pass through, which is more stable. | | `trail` | Leave a trail | off | A faint path of the tips. | | `palette` | Palette | ink | The strip colours. Recolour is also a live control, tested separately. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `fixtures/ribbon-tips-3.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/ribbon-wind.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/ribbons.png` | Eight strips in a breeze, seed 3, a golden frame with no NaNs. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. A seeded breeze run of 600 steps has no NaNs and no exploded segment, and tip positions match a file. Recolour of a strip is read back and shown in a golden. A golden breeze frame is checked. No network.