# 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. ## home-to-studio Twelve hops, addresses in documentation-range IPv4 (192.0.2.0/24 and 198.51.100.0/24), rtts and coordinates in `fixtures/path-home.json`. The mid-path screenshot is hop 6. Arrival is hop 12, labelled with `dest_name`. ## Screenshot tolerance 8 levels, 98% of pixels. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | How this packet arrived | Shown on the first hop. | | `dest_name` | Destination label | the studio | A friendly name for the last hop. | | `map` | Show a map | on | A simple map of hop coordinates from the fixture, not a live geolocation API. | | `timings` | Show hop timings | on | The rtt figures from the fixture file. | | `path` | Fixture path | home-to-studio | A shipped traceroute-like file. No live probing in the checks. | ## 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/path-home.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/hops.png` | The fixture traceroute to the studio, seven hops, 111 ms. | ## 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 fixture path is illustrated hop for hop, in order, with the labels and rtts from the file. Checks hook fetches and child processes so no live traceroute or map API can sneak in. Golden frames cover a first hop, a mid hop, a map, and the arrival. No raw sockets.