# 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. ## Coast start Node `c0` ways: `left` → `c1`, `straight` → `c2`, `right` → `c3`. No `back`. ## Tally fixtures | Votes | Winner | Reason | | --- | --- | --- | | 3 straight, 2 left | straight | plurality | | 2 right, 2 left | right | tie order, right before left | | 2 straight, 2 right | straight | tie order, straight first | | none | straight | default | The same cases are in `fixtures/roadtrip-tallies.json`. ## Session `fixtures/coast-session.json` is the authority for the 8-turn path and for the arrival node `c-end`. ## Screenshot tolerance 8 levels, 98% of pixels. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Where to next? | Shown over the view. | | `turn_seconds` | Seconds per turn | 8 | From 4 to 20. Tests inject the clock. | | `chat` | Show a chatter strip | off | A short, local list of canned lines in this version, not a live chat. | | `names` | Show voter counts | on | The number of votes for each way is visible during the turn. | | `route` | Fixture route | coast | A shipped graph of views and turns. No live street-level API. | ## 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/coast-session.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/roadtrip-tallies.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/road.png` | Five seconds left, 62% of votes for the coastal road. | ## 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. Vote-tally and turn-protocol tests cover plurality, the documented tie order, and a turn with no votes. A scripted session on fixture imagery follows a documented path. Checks hook fetches so no live street-level API can sneak in. The clock is injected. No public vote server.