# 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. ## Formulas The exact formulas, with constants, are `fixtures/curves-formulas.md` and the point file is the authority for values. A short restatement: the spherical helix is a rhumb line on the unit sphere with `turns` windings from the south pole to the north; the torus knot is (p, q) = (2, 3) on a torus R=2, r=0.6; the Lissajous is (sin(3θ), sin(4θ), sin(5θ)) with θ = 2πt. ## Screenshot tolerance 8 levels, 98% of pixels. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A walk along a curve | Shown in the first room. | | `turns` | Default helix turns | 5 | From 2 to 12, for the spherical helix room. | | `ribbon` | Draw a ribbon | on | A thin surface along the tangent, not only a tube. | | `guides` | Show the generating sphere | on | A faint sphere the helix lives on. | | `room` | Starting room | helix | Three shipped curves. The museum contains all three. | ## 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 | | --- | --- | | `design.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/curves-cameras.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/curves-formulas.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/curves-points.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/curve.png` | Five turns of a spherical helix, documented points marked. | ## 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. Each parameterized curve passes through documented points within 1e-4, and the spherical helix stays on the unit sphere at 64 samples. Camera poses along a ride match a file. Golden views are taken in each room and along the path. No network.