# 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. ## Parameters (bar, millimetres) | Key | Default | Range | | --- | --- | --- | | width | 71 | 60–80 | | height | 147 | 120–170 | | thickness | 8.2 | 6–12 | | radius | 12 | 0–20, and at most half of min(width, height) | | bump_count | 2 | 1, 2 or 3 (3 refused on fold) | | bump_size | 10 | 8–16 | | material | `stone` | `stone`, `glass`, `matte` | The mesh measures (bounding box, bump centre positions) for the default and for the fixture are `fixtures/phone-measures.json`. ## State string A query such as `b=bar&w=71&h=147&t=8.2&r=12&c=2&s=10&m=stone`. Unknown keys are refused. The fixture file is the authority for its own string. ## Screenshot tolerance 8 levels, 98% of pixels, 1600 by 1000, same camera for a given body family. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Kit a handset | Shown above the stage. | | `share_prefix` | Share URL prefix | https://example.invalid/p/ | The prefix of a shareable URL. Tests use this exact host. | | `camera_light` | A second light | on | A rim light on the opposite side of the key light. | | `annotations` | Show size annotations | off | Dimension arrows on the render. | | `body` | Body family | bar | A slab, or a two-leaf fold with a documented hinge gap. | ## 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/phone-alpha.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/phone-measures.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/handset.png` | The default midnight handset and the four mesh controls. | ## 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 control changes a documented mesh measure, checked in millimetres. Illegal combinations are refused. A fixture design renders to a golden image and round-trips through a shareable state URL. No brand assets and no network.