Flight globe
Fixture flight logs plotted on a globe and a chart, with documented coordinates and distances, and no live aviation API.
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/flight-globe- Version
- 0.2.2
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/flight-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 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.Flight globe
What this builds
A globe and a small chart of a person's (or a sample) flying. Routes are great-circle arcs between airports in a shipped list. Hours and distances come from a fixture log, not from a live aviation API. The sample log is fictional. The person can filter by year and click a route.
Read
spekkr.inputs.jsonfirst.titlesits over the globe.yearfilters the log.logchooses the fixture.arcsandchartchange the picture.Out of scope
- A live airline, ADS-B, or tracking API in the checks.
- A real person's private log unless they later load one locally.
- A claim of official hours.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Projection and distance
- Airports are in
fixtures/airports.jsonwith lat, lon, and id. - A great-circle distance uses the haversine formula and a radius of 6371 km. Fixture pairs in
design.mdmatch to 1 km. - A log row with from, to, date, and duration projects to the documented arc endpoints.
Accept when: every distance fixture matches to 1 km, and every sample-year row projects to the listed endpoints.
R2. Filters and hooks
year2025 onsample-yearleaves the set infixtures/log-2025.json.allleaves every row.- A fetch hook fails if a known aviation or map-tile host is contacted.
- The hours chart, if on, sums duration by month and matches
fixtures/hours-2025.jsonfor that filter.
Accept when: the filter and the month sums match, and the hook stays quiet.
R3. Frames and files
- Goldens: the globe with all sample-year arcs, a close arc, the hours chart, and the 2025-filtered globe.
- One command runs distances, filters, the hook, and writes the frames. No network.
Accept when: the command passes for both logs, 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
Fixture flight logs project to documented coordinates and haversine distances, to 1 km. A year filter and a hours-by-month chart match shipped files. Golden globe and chart views are checked. A fetch hook fails if a live aviation API is contacted.
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 local log later, how the sample log is fictional, and how to run the checks.
# Flight globe ## What this builds A globe and a small chart of a person's (or a sample) flying. Routes are great-circle arcs between airports in a shipped list. Hours and distances come from a fixture log, not from a live aviation API. The sample log is fictional. The person can filter by year and click a route. Read `spekkr.inputs.json` first. `title` sits over the globe. `year` filters the log. `log` chooses the fixture. `arcs` and `chart` change the picture. ## Out of scope - A live airline, ADS-B, or tracking API in the checks. - A real person's private log unless they later load one locally. - A claim of official hours. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Projection and distance - Airports are in `fixtures/airports.json` with lat, lon, and id. - A great-circle distance uses the haversine formula and a radius of 6371 km. Fixture pairs in `design.md` match to 1 km. - A log row with from, to, date, and duration projects to the documented arc endpoints. Accept when: every distance fixture matches to 1 km, and every sample-year row projects to the listed endpoints. ### R2. Filters and hooks - `year` 2025 on `sample-year` leaves the set in `fixtures/log-2025.json`. `all` leaves every row. - A fetch hook fails if a known aviation or map-tile host is contacted. - The hours chart, if on, sums duration by month and matches `fixtures/hours-2025.json` for that filter. Accept when: the filter and the month sums match, and the hook stays quiet. ### R3. Frames and files - Goldens: the globe with all sample-year arcs, a close arc, the hours chart, and the 2025-filtered globe. - One command runs distances, filters, the hook, and writes the frames. No network. Accept when: the command passes for both logs, 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 Fixture flight logs project to documented coordinates and haversine distances, to 1 km. A year filter and a hours-by-month chart match shipped files. Golden globe and chart views are checked. A fetch hook fails if a live aviation API is contacted. ## 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 local log later, how the sample log is fictional, and how to run the checks.
-
design.mdHaversine distances, fixture logs, and the year filter.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.
Distance fixtures
Pairs (for example LON–JFK, and shorter European pairs) and expected kilometres are
fixtures/distances.json. Tests compare to 1 km. The sample log is fictional, with invented call signs, inlogs/sample-year.json.Screenshot tolerance
8 levels, 98% of pixels. Arc endpoints in the image should also fall inside a 6 px circle of the projected airport.
Inputs
Key Label Default Notes titleTitle Where the hours went Shown over the globe. yearYear filter 2025 A year, or all. The fixture log is tagged by date.arcsDraw great-circle arcs on Routes are arcs, not straight lines in the projection. chartShow a hours chart on A bar or line chart of hours by month next to the globe. logFixture log sample-year A shipped flight log. No live airline or tracking 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 design.mdA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/airports.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/distances.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/hours-2025.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/log-2025.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.logs/sample-year.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/globe.pngFixture 2025 flights drawn on a globe, with hours in the air beside it. 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.
- Fixture flight logs project to documented coordinates and haversine distances, to 1 km. A year filter and a hours-by-month chart match shipped files. Golden globe and chart views are checked. A fetch hook fails if a live aviation API is contacted.
# 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. ## Distance fixtures Pairs (for example LON–JFK, and shorter European pairs) and expected kilometres are `fixtures/distances.json`. Tests compare to 1 km. The sample log is fictional, with invented call signs, in `logs/sample-year.json`. ## Screenshot tolerance 8 levels, 98% of pixels. Arc endpoints in the image should also fall inside a 6 px circle of the projected airport. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Where the hours went | Shown over the globe. | | `year` | Year filter | 2025 | A year, or `all`. The fixture log is tagged by date. | | `arcs` | Draw great-circle arcs | on | Routes are arcs, not straight lines in the projection. | | `chart` | Show a hours chart | on | A bar or line chart of hours by month next to the globe. | | `log` | Fixture log | sample-year | A shipped flight log. No live airline or tracking 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 | | --- | --- | | `design.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/airports.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/distances.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/hours-2025.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/log-2025.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `logs/sample-year.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` | Fixture 2025 flights drawn on a globe, with hours in the air beside it. | ## 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 flight logs project to documented coordinates and haversine distances, to 1 km. A year filter and a hours-by-month chart match shipped files. Golden globe and chart views are checked. A fetch hook fails if a live aviation API is contacted.
-
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. - Projection and distance (R1). Build what
R1. Projection and distanceasks for, to the numbers indesign.md. In particular: Airports are infixtures/airports.jsonwith lat, lon, and id. Check: theR1. Projection and distanceacceptance checks pass. - Filters and hooks (R2). Build what
R2. Filters and hooksasks for, to the numbers indesign.md. In particular:year2025 onsample-yearleaves the set infixtures/log-2025.json.allleaves every row. Check: theR2. Filters and hooksacceptance checks pass. - Frames and files (R3). Build what
R3. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: the globe with all sample-year arcs, a close arc, the hours chart, and the 2025-filtered globe. 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. **Projection and distance (R1).** Build what `R1. Projection and distance` asks for, to the numbers in `design.md`. In particular: Airports are in `fixtures/airports.json` with lat, lon, and id. Check: the `R1. Projection and distance` acceptance checks pass. 3. **Filters and hooks (R2).** Build what `R2. Filters and hooks` asks for, to the numbers in `design.md`. In particular: `year` 2025 on `sample-year` leaves the set in `fixtures/log-2025.json`. `all` leaves every row. Check: the `R2. Filters and hooks` 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 globe with all sample-year arcs, a close arc, the hours chart, and the 2025-filtered globe. 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, WebGL
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall 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.