Radio globe

A globe of radio stations from a fixture list, at documented coordinates, playing a local audio file rather than a live network.

This is a small site spec on Spekkr, published by lume. 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
lume/radio-globe
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/lume/radio-globe/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 lume.

What does the result look like?

Radio globe: heroRadio globe: loop

What can I customize?

Station set A shipped list of fictional stations with coordinates and a local audio fixture.

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.

    Radio globe

    What this builds

    A globe with marks for radio stations. Clicking a mark plays a local fixture loop, not a live radio network. The stations are fictional, with documented coordinates. A hook fails if a known live-radio host is contacted. The look is original.

    Read spekkr.inputs.json first. title sits over the globe. volume is the default. set chooses the list. labels and night change the picture. The sun position for night is a fixture, not a live clock, unless tests inject one.

    Out of scope

    • A live radio network or a commercial stream directory in the checks.
    • A claim that the stations are real broadcasters.
    • Network in the checks.

    Requirements

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

    R1. Coordinates and play
    • Each station has a name, lat, lon, and a local audio path. Fixture positions in fixtures/radio-stations.json are drawn at the documented projected pixel, within 3 px, on the default camera.
    • Clicking a listed station starts its local file, sets a playing flag, and shows its name if labels are on.
    • A fetch hook fails if a known radio or stream host is contacted.

    Accept when: every listed station projects within 3 px, play requests the local file, and the hook stays quiet.

    R2. Frames and files
    • Goldens: the sample globe, a selected station, a playing chrome, and the tiny set.
    • One command projects, plays, hooks, and writes the frames. No network.

    Accept when: the command passes for both sets, and the frames match the goldens.

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

    R4. Checks and report
    • One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them.
    • Checks do not need a network, a paid API, or physical hardware.

    Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it.

    Verification

    Fixture stations appear at documented latitudes and longitudes, checked in projection. Click-to-play uses a local audio fixture, not a live radio network; a fetch hook fails otherwise. Golden frames are taken. Stations are fictional.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to add a fixture station, how play is local, and how to run the checks.
    # Radio globe
    
    ## What this builds
    
    A globe with marks for radio stations. Clicking a mark plays a local
    fixture loop, not a live radio network. The stations are fictional, with
    documented coordinates. A hook fails if a known live-radio host is
    contacted. The look is original.
    
    Read `spekkr.inputs.json` first. `title` sits over the globe. `volume` is
    the default. `set` chooses the list. `labels` and `night` change the
    picture. The sun position for night is a fixture, not a live clock, unless
    tests inject one.
    
    ## Out of scope
    
    - A live radio network or a commercial stream directory in the checks.
    - A claim that the stations are real broadcasters.
    - Network in the checks.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Coordinates and play
    
    - Each station has a name, lat, lon, and a local audio path. Fixture
      positions in `fixtures/radio-stations.json` are drawn at the documented
      projected pixel, within 3 px, on the default camera.
    - Clicking a listed station starts its local file, sets a playing flag,
      and shows its name if labels are on.
    - A fetch hook fails if a known radio or stream host is contacted.
    
    Accept when: every listed station projects within 3 px, play requests the
    local file, and the hook stays quiet.
    
    ### R2. Frames and files
    
    - Goldens: the sample globe, a selected station, a playing chrome, and the
      tiny set.
    - One command projects, plays, hooks, and writes the frames. No network.
    
    Accept when: the command passes for both sets, and the frames match the
    goldens.
    
    ### R3. 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.
    
    ### R4. Checks and report
    
    - One command runs every acceptance check at the defaults and at the
      person's inputs, including golden frames where a requirement asks for
      them.
    - Checks do not need a network, a paid API, or physical hardware.
    
    Accept when: the command passes at the defaults, and a deliberately broken
    fixture or a wrong price fails it.
    
    ## Verification
    
    Fixture stations appear at documented latitudes and longitudes, checked in
    projection. Click-to-play uses a local audio fixture, not a live radio
    network; a fetch hook fails otherwise. Golden frames are taken. Stations
    are fictional.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to add a fixture station, how play is local, and how
      to run the checks.
    

    Open spec.md as plain text

  • design.md Fixture stations, projection, and the local-audio rule.

    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.

    Projection

    A simple equirectangular or a documented globe projection, in fixtures/radio-projection.json, with the camera. Station coordinates are fictional.

    Screenshot tolerance

    8 levels, 98% of pixels. Projection is a geometric check.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA world of roomsShown over the globe.
    volumeDefault volume0.8From 0 to 1.
    labelsLabel stationsonA name next to a selected mark.
    nightNight sideonA dark wash on the night half, from a fixture sun position.
    setStation setsampleA shipped list of fictional stations with coordinates and a local audio fixture.

    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/radio-projection.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/radio-stations.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/globe.pngLisbon night desk playing from the fixture list, volume 0.8.

    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. Fixture stations appear at documented latitudes and longitudes, checked in projection. Click-to-play uses a local audio fixture, not a live radio network; a fetch hook fails otherwise. Golden frames are taken. Stations are fictional.
    # 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.
    
    ## Projection
    
    A simple equirectangular or a documented globe projection, in
    `fixtures/radio-projection.json`, with the camera. Station coordinates are
    fictional.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. Projection is a geometric check.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A world of rooms | Shown over the globe. |
    | `volume` | Default volume | 0.8 | From 0 to 1. |
    | `labels` | Label stations | on | A name next to a selected mark. |
    | `night` | Night side | on | A dark wash on the night half, from a fixture sun position. |
    | `set` | Station set | sample | A shipped list of fictional stations with coordinates and a local audio fixture. |
    
    ## 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/radio-projection.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/radio-stations.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/globe.png` | Lisbon night desk playing from the fixture list, volume 0.8. |
    
    
    ## 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. Fixture stations appear at documented latitudes and longitudes, checked
    in projection. Click-to-play uses a local audio fixture, not a live radio
    network; a fetch hook fails otherwise. Golden frames are taken. Stations
    are fictional.
    

    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. Coordinates and play (R1). Build what R1. Coordinates and play asks for, to the numbers in design.md. In particular: Each station has a name, lat, lon, and a local audio path. Fixture positions in fixtures/radio-stations.json are drawn at the documented projected pixel, within 3 px, on the default camera. Check: the R1. Coordinates and play acceptance checks pass.
    3. Frames and files (R2). Build what R2. Frames and files asks for, to the numbers in design.md. In particular: Goldens: the sample globe, a selected station, a playing chrome, and the tiny set. Check: the R2. Frames and files acceptance checks pass.
    4. Inputs (R3). Build what R3. 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 R3. Inputs acceptance checks pass.
    5. Checks and report (R4). Build what R4. Checks and report asks for, to the numbers in design.md. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the R4. Checks and report 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.
    # 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. **Coordinates and play (R1).** Build what `R1. Coordinates and play`
    asks for, to the numbers in `design.md`. In particular: Each station has a
    name, lat, lon, and a local audio path. Fixture positions in
    `fixtures/radio-stations.json` are drawn at the documented projected
    pixel, within 3 px, on the default camera.
       Check: the `R1. Coordinates and play` acceptance checks pass.
    
    3. **Frames and files (R2).** Build what `R2. Frames and files` asks for,
    to the numbers in `design.md`. In particular: Goldens: the sample globe, a
    selected station, a playing chrome, and the tiny set.
       Check: the `R2. Frames and files` acceptance checks pass.
    
    4. **Inputs (R3).** Build what `R3. 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 `R3. Inputs` acceptance checks pass.
    
    5. **Checks and report (R4).** Build what `R4. Checks and report` asks
    for, to the numbers in `design.md`. In particular: One command runs every
    acceptance check at the defaults and at the person's inputs, including
    golden frames where a requirement asks for them.
       Check: the `R4. Checks and report` 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.
    

    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/GeistMono.ttf Geist Mono 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.115 Nov 2026Project continent silhouettes with dusk shading and a lat-lon grid, and add an animated loop.
  • 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.