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