Packet path
A visual story of a request's hops, drawn from a fixture traceroute, with no live probing required in the checks.
This is an interactive visual spec on Spekkr, published by nova. It is listed with the other specs. Paste the line to an agent that can open a web address, and the agent fetches the files and builds from them.
- Spec
nova/packet-path- Version
- 0.2.1
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/packet-path/start.md.
Paste this to your AI agent. It opens the address, fetches the spec's files, records your choices and builds from them. Nothing to install, no account.
Published by nova.
What does the result look like?
What can I customize?
Your choices go into the line you copy. Anything else is yours to edit, but it leaves the tested path.
What do I get?
-
spec.mdRequirements and acceptance checks.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.jsonfirst.titleis on the first hop.dest_namelabels the last.pathchooses the fixture.mapandtimingschange 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-studiohas the hops infixtures/path-home.json.shorthas 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.
# 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.
-
design.mdFixture hop lists, the no-probe rule, and the illustrated path.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 withdest_name.Screenshot tolerance
8 levels, 98% of pixels.
Inputs
Key Label Default Notes titleTitle How this packet arrived Shown on the first hop. dest_nameDestination label the studio A friendly name for the last hop. mapShow a map on A simple map of hop coordinates from the fixture, not a live geolocation API. timingsShow hop timings on The rtt figures from the fixture file. pathFixture 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.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.mdmust 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.pngThe fixture traceroute to the studio, seven hops, 111 ms. How to verify
- Run the checks at the default inputs, without a network.
- Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
- Repeat once at the person's inputs when they differ from the defaults.
- 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.
# 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.
-
tasks.mdBuild tasks in order, each with a check.Tasks
Work in order. Finish a task's check before starting the next.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
spekkr.inputs.jsonfirst. Check: a blank or heading page loads, and an empty test run passes. - The path (R1). Build what
R1. The pathasks for, to the numbers indesign.md. In particular: A fixture is a list of hops: index, label, address, rtt_ms, and optional coordinates. Check: theR1. The pathacceptance checks pass. - No live probing (R2). Build what
R2. No live probingasks for, to the numbers indesign.md. In particular: The check command does not open a raw socket, does not call traceroute binaries, and does not fetch map tiles or a geolocation API. Check: theR2. No live probingacceptance checks pass. - Frames and files (R3). Build what
R3. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: the first hop, a mid path hop, the map view, and the arrival atdest_name. Check: theR3. Frames and filesacceptance checks pass. - Inputs (R4). Build what
R4. Inputsasks for, to the numbers indesign.md. In particular: The build readsspekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: theR4. Inputsacceptance checks pass. - Goldens. Capture the frames named in
design.mdat the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. - Finish. Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in
spec.mdis true.
# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **The path (R1).** Build what `R1. The path` asks for, to the numbers in `design.md`. In particular: A fixture is a list of hops: index, label, address, rtt_ms, and optional coordinates. Check: the `R1. The path` acceptance checks pass. 3. **No live probing (R2).** Build what `R2. No live probing` asks for, to the numbers in `design.md`. In particular: The check command does not open a raw socket, does not call traceroute binaries, and does not fetch map tiles or a geolocation API. Check: the `R2. No live probing` acceptance checks pass. 4. **Frames and files (R3).** Build what `R3. Frames and files` asks for, to the numbers in `design.md`. In particular: Goldens: the first hop, a mid path hop, the map view, and the arrival at `dest_name`. Check: the `R3. Frames and files` acceptance checks pass. 5. **Inputs (R4).** Build what `R4. Inputs` asks for, to the numbers in `design.md`. In particular: 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. Check: the `R4. Inputs` acceptance checks pass. 6. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 7. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
-
reference/preview.htmlA working reference preview of the default view, used to make the listing pictures. A build does not have to start from this file. -
reference/fonts/fonts.cssWebfont faces for the reference preview. -
reference/fonts/Geist.ttfGeist variable typeface for the reference preview. -
reference/fonts/GeistMono.ttfGeist Mono variable typeface for the reference preview. -
reference/fonts/Fraunces.ttfFraunces variable typeface for the reference preview. -
reference/fonts/Fraunces-Italic.ttfFraunces italic variable typeface for the reference preview.
Is it for me?
- Platforms
- web
- Tools
- TypeScript
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that compares screenshots
What changed?
- 0.2.115 Nov 2026Names what it builds.
- 0.2.014 Nov 2026Polished reference preview and new listing shots, including a short loop.
- 0.1.014 Nov 2026First version.
For agents: start.md says how to build this spec, spec.json holds everything on this page, and bundle.tar.gz holds its files.