# 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. ## Tiny graph Nodes and directed edges are `graphs/tiny.json`. The oak → moon path is `[oak, grove, river, moon]` (3 hops). The pair `oak` → `isolated` is `none` when directed, and `[oak, isolated]` when undirected if that edge exists as a reverse of `isolated → oak` — the file is the authority. `campus` has at least 30 nodes and its own fixture pairs in `fixtures/campus-paths.json`. ## Screenshot tolerance 8 levels, 98% of pixels. The on-page path text must also match the fixture list exactly. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | How many steps between them? | Shown above the search. | | `from` | Default from | oak | An article id in the fixture graph. | | `to` | Default to | moon | An article id in the fixture graph. | | `animate` | Animate the path | on | Nodes appear in order. Tests may settle at the end. | | `undirected` | Ignore direction | off | If on, edges are treated as two-way. The default graph is directed as shipped. | | `graph` | Fixture graph | tiny | A shipped graph of articles and links. No live encyclopedia. | ## 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/campus-paths.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `graphs/tiny.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/graph.png` | The shortest fixture path from oak to moon, four steps, drawn on the graph. | ## 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. Shortest-path tests run on a fixture graph, not a live encyclopedia. The UI shows the documented path (and a no-path state). A fetch hook fails if an encyclopedia host is contacted. Golden frames are taken. Names in the product are original.