# 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. ## Climb Altitude `h(t) = 35786 * t * t` km (ease-in quadratic), t from 0 to 1. Times when the camera hits table heights: tropopause t = sqrt(17/35786), and so on. The exact t values and windows are `fixtures/elevator-heights.json`. Tests compare to that file, within 1 km and within 0.002 of t. ## Not to scale From 0 to 100 km the tether is drawn at 1 px per 0.2 km. Above that a break mark appears and the remaining climb to 35786 km is drawn in a second scale, 1 px per 80 km, as labelled on the ruler. ## Screenshot tolerance 8 levels, 98% of pixels. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A ride to orbit | Shown on the ground frame. | | `anchor_lat` | Anchor latitude, degrees | 0 | From -35 to 35. The default is on the equator. | | `facts` | Show altitude facts | on | A caption at each documented height. | | `atmosphere` | Show the atmosphere bands | on | A colour wash for troposphere, stratosphere and above. | | `units` | Altitude units | km | Labels only. The table in design.md is in kilometres and always holds. | ## 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/elevator-facts.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/elevator-heights.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/ride.png` | The climber at 18 400 km on the tether, Earth below. | ## 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. Altitude labels and camera position are tested against a height table, to 1 km. Golden frames are taken at ground, tropopause, a stratosphere point, and orbit. Units only change labels. No live orbital data and no network.