Vote roadtrip

A shared roadtrip where votes steer the next turn, checked with fixture imagery and a documented path, not a live street view.

This is a browser game 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/vote-roadtrip
Version
0.2.2
Published by
nova
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/nova/vote-roadtrip/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?

Vote roadtrip: heroVote roadtrip: loop

What can I customize?

Fixture route A shipped graph of views and turns. No live street-level API.

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.md Requirements and acceptance checks.

    Vote roadtrip

    What this builds

    A view of a road, four possible ways, and a countdown. People vote on the next way. When the turn ends, the plurality wins, ties break by a documented order, and the view advances along a graph. In checks the views are fixture images and the voters are scripted; no live street-level service is used. The route and the pictures are original.

    Read spekkr.inputs.json first. title sits over the view. turn_seconds is the window. route chooses the fixture graph. names shows counts. chat is a local strip and is off in the default checks.

    Out of scope

    • A live commercial street-level API in the checks.
    • A real public vote server in the checks; voters are a fake in-process room.
    • Vehicle physics.

    Requirements

    Each requirement has an id. Checks name the id they cover.

    R1. The graph
    • A route is a graph of nodes, each with a view image, and edges labelled left, straight, right, or back (not every node has every way).
    • The starting node of coast is c0. The starting node of grid is g0.
    • A missing way cannot be voted for and is not drawn.

    Accept when: both routes load, c0 has the ways listed in design.md, and a vote for a missing way is refused.

    R2. Votes and ties
    • During a turn, each voter id may cast or change one vote.
    • At the end of the turn, the way with the most votes is taken. A tie is broken in the order straight, right, left, back.
    • If no vote was cast, the default way straight is taken if it exists, else right, else the first listed edge.

    Accept when: the tally fixtures in design.md produce the documented chosen way, including a 2–2 tie and a no-vote turn.

    R3. A scripted session
    • fixtures/coast-session.json is a list of turns, votes, and the expected node after each turn. Starting from c0, the session ends at c-end after 8 turns.
    • Views are the fixture images, never a network fetch. A hook around fetch fails the test if a street-view host is contacted.

    Accept when: the session follows the documented path, and the four screenshots (first view, mid-vote, after the first turn, arrival) match the goldens.

    R4. Files
    • One command runs graph, tally, session, and fetch-hook tests, and writes the screenshots. The clock is injected. No network.

    Accept when: the command passes for both routes.

    R5. 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

    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.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to run a local room, how to add a route, and how to run the checks.
    # Vote roadtrip
    
    ## What this builds
    
    A view of a road, four possible ways, and a countdown. People vote on the
    next way. When the turn ends, the plurality wins, ties break by a
    documented order, and the view advances along a graph. In checks the views
    are fixture images and the voters are scripted; no live street-level
    service is used. The route and the pictures are original.
    
    Read `spekkr.inputs.json` first. `title` sits over the view.
    `turn_seconds` is the window. `route` chooses the fixture graph. `names`
    shows counts. `chat` is a local strip and is off in the default checks.
    
    ## Out of scope
    
    - A live commercial street-level API in the checks.
    - A real public vote server in the checks; voters are a fake in-process
      room.
    - Vehicle physics.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. The graph
    
    - A route is a graph of nodes, each with a view image, and edges labelled
      `left`, `straight`, `right`, or `back` (not every node has every way).
    - The starting node of `coast` is `c0`. The starting node of `grid` is
      `g0`.
    - A missing way cannot be voted for and is not drawn.
    
    Accept when: both routes load, `c0` has the ways listed in `design.md`,
    and a vote for a missing way is refused.
    
    ### R2. Votes and ties
    
    - During a turn, each voter id may cast or change one vote.
    - At the end of the turn, the way with the most votes is taken. A tie is
      broken in the order `straight`, `right`, `left`, `back`.
    - If no vote was cast, the default way `straight` is taken if it exists,
      else `right`, else the first listed edge.
    
    Accept when: the tally fixtures in `design.md` produce the documented
    chosen way, including a 2–2 tie and a no-vote turn.
    
    ### R3. A scripted session
    
    - `fixtures/coast-session.json` is a list of turns, votes, and the
      expected node after each turn. Starting from `c0`, the session ends at
      `c-end` after 8 turns.
    - Views are the fixture images, never a network fetch. A hook around fetch
      fails the test if a street-view host is contacted.
    
    Accept when: the session follows the documented path, and the four
    screenshots (first view, mid-vote, after the first turn, arrival) match
    the goldens.
    
    ### R4. Files
    
    - One command runs graph, tally, session, and fetch-hook tests, and writes
      the screenshots. The clock is injected. No network.
    
    Accept when: the command passes for both routes.
    
    ### R5. 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
    
    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.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to run a local room, how to add a route, and how to
      run the checks.
    

    Open spec.md as plain text

  • design.md The route graph, tie-break order, and the scripted session 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.

    Coast start

    Node c0 ways: left → c1, straight → c2, right → c3. No back.

    Tally fixtures

    VotesWinnerReason
    3 straight, 2 leftstraightplurality
    2 right, 2 leftrighttie order, right before left
    2 straight, 2 rightstraighttie order, straight first
    nonestraightdefault

    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

    KeyLabelDefaultNotes
    titleTitleWhere to next?Shown over the view.
    turn_secondsSeconds per turn8From 4 to 20. Tests inject the clock.
    chatShow a chatter stripoffA short, local list of canned lines in this version, not a live chat.
    namesShow voter countsonThe number of votes for each way is visible during the turn.
    routeFixture routecoastA 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.

    FixtureRole
    fixtures/coast-session.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/roadtrip-tallies.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    spekkr.inputs.jsonA 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.

    FileWhat it shows
    shots/road.pngFive 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.
    # 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.
    

    Open design.md as plain text

  • tasks.md Build tasks in order, each with a check.

    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 graph (R1). Build what R1. The graph asks for, to the numbers in design.md. In particular: A route is a graph of nodes, each with a view image, and edges labelled left, straight, right, or back (not every node has every way). Check: the R1. The graph acceptance checks pass.
    3. Votes and ties (R2). Build what R2. Votes and ties asks for, to the numbers in design.md. In particular: During a turn, each voter id may cast or change one vote. Check: the R2. Votes and ties acceptance checks pass.
    4. A scripted session (R3). Build what R3. A scripted session asks for, to the numbers in design.md. In particular: fixtures/coast-session.json is a list of turns, votes, and the expected node after each turn. Starting from c0, the session ends at c-end after 8 turns. Check: the R3. A scripted session acceptance checks pass.
    5. Files (R4). Build what R4. Files asks for, to the numbers in design.md. In particular: One command runs graph, tally, session, and fetch-hook tests, and writes the screenshots. The clock is injected. No network. Check: the R4. Files acceptance checks pass.
    6. Inputs (R5). Build what R5. 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 R5. Inputs acceptance checks pass.
    7. 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.
    8. 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.
    # 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 graph (R1).** Build what `R1. The graph` asks for, to the numbers
    in `design.md`. In particular: A route is a graph of nodes, each with a
    view image, and edges labelled `left`, `straight`, `right`, or `back` (not
    every node has every way).
       Check: the `R1. The graph` acceptance checks pass.
    
    3. **Votes and ties (R2).** Build what `R2. Votes and ties` asks for, to
    the numbers in `design.md`. In particular: During a turn, each voter id
    may cast or change one vote.
       Check: the `R2. Votes and ties` acceptance checks pass.
    
    4. **A scripted session (R3).** Build what `R3. A scripted session` asks
    for, to the numbers in `design.md`. In particular:
    `fixtures/coast-session.json` is a list of turns, votes, and the expected
    node after each turn. Starting from `c0`, the session ends at `c-end`
    after 8 turns.
       Check: the `R3. A scripted session` acceptance checks pass.
    
    5. **Files (R4).** Build what `R4. Files` asks for, to the numbers in
    `design.md`. In particular: One command runs graph, tally, session, and
    fetch-hook tests, and writes the screenshots. The clock is injected. No
    network.
       Check: the `R4. Files` acceptance checks pass.
    
    6. **Inputs (R5).** Build what `R5. 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 `R5. Inputs` acceptance checks pass.
    
    7. **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.
    
    8. **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.
    

    Open tasks.md as plain text

  • reference/preview.html A 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.css Webfont faces for the reference preview.
  • reference/fonts/Geist.ttf Geist variable typeface for the reference preview.
  • reference/fonts/Fraunces.ttf Fraunces variable typeface for the reference preview.
  • reference/fonts/Fraunces-Italic.ttf Fraunces 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 runner install a tool that compares screenshots

What changed?

  • 0.2.215 Nov 2026Names what it builds.
  • 0.2.114 Nov 2026Add animated loop to the listing shots.
  • 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.