# Packet path ## What this builds A hop-by-hop story of how a request reached a server: each hop is a name, an address, a timing, and a place on a simple map. In the checks, and in the default demo, the path is a fixture file that looks like a traceroute, not a live probe. A later hook can load a real path, but a live probe is out of scope for acceptance. The copy is original. Read `spekkr.inputs.json` first. `title` is on the first hop. `dest_name` labels the last. `path` chooses the fixture. `map` and `timings` change the chrome. Coordinates in the fixture are used as-is; no geolocation lookup is done in the checks. ## Out of scope - Live traceroute, ICMP, or raw sockets in the checks. - A live geolocation or map-tile API in the checks. - A claim that the fixture is a real person's path. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. The path - A fixture is a list of hops: index, label, address, rtt_ms, and optional coordinates. - `home-to-studio` has the hops in `fixtures/path-home.json`. `short` has three hops. - The page illustrates every hop in order. A missing hop index is refused when the file is loaded. Accept when: both fixtures load, every hop is shown in order, and a file with a skipped index is refused. ### R2. No live probing - The check command does not open a raw socket, does not call traceroute binaries, and does not fetch map tiles or a geolocation API. - A hook around fetch and around child processes fails the test if a listed probe or map host, or a traceroute binary, is invoked. Accept when: the hook stays quiet during a full render of both fixtures. ### R3. Frames and files - Goldens: the first hop, a mid path hop, the map view, and the arrival at `dest_name`. - One command loads the fixtures, runs the hook, and writes the frames. Accept when: the command passes, and the frames match the goldens. ### R4. 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. ## Verification 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. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to load a fixture, how a later live hook could be added, and how to run the checks.