Space elevator
A continuous ride from the ground to orbit, with altitude labels checked against a height table and goldens at three stops.
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/space-elevator- Version
- 0.2.2
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/space-elevator/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.Space elevator
What this builds
A vertical journey up a tether, from a ground anchor to a station in orbit. The camera climbs continuously. At documented heights a fact appears. The numbers are a simple Earth model, listed in a table, not a live ephemeris. The art is original.
Read
spekkr.inputs.jsonfirst.titleis on the ground.anchor_latonly changes a label and the length of the ground track; the height table is the same.factsandatmospherechange the chrome.unitschange labels only.Out of scope
- A real engineering proposal or a claim that this tether can be built.
- A live weather or orbital API.
- A ride that needs a GPU cluster.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. The height table
- Heights in kilometres above mean sea level: ground 0, tropopause 17 (at the equator in this model), stratopause 50, Karman 100, station 35786.
- The camera's altitude at a normalised climb t in [0, 1] is the ease in
design.md, and labels appear when the camera is within 2% of a table height. - The tether is drawn as a line from 0 to 35786 km, not to scale in the last segment, with a break mark as in
design.md.
Accept when: at the documented t values the camera altitude matches the table within 1 km, and each label is present in the listed window.
R2. Frames
- Goldens at ground (t = 0), tropopause, a stratosphere mid-point, and the station.
- Facts, if on, match the text in
fixtures/elevator-facts.json.
Accept when: the four frames match the goldens, including the fact text when the option is on.
R3. Files
- One command runs the height tests and writes the frames. No network.
Accept when: the command passes in both unit labels.
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
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.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to ride, how to read the scales, and how to run the checks.
# Space elevator ## What this builds A vertical journey up a tether, from a ground anchor to a station in orbit. The camera climbs continuously. At documented heights a fact appears. The numbers are a simple Earth model, listed in a table, not a live ephemeris. The art is original. Read `spekkr.inputs.json` first. `title` is on the ground. `anchor_lat` only changes a label and the length of the ground track; the height table is the same. `facts` and `atmosphere` change the chrome. `units` change labels only. ## Out of scope - A real engineering proposal or a claim that this tether can be built. - A live weather or orbital API. - A ride that needs a GPU cluster. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. The height table - Heights in kilometres above mean sea level: ground 0, tropopause 17 (at the equator in this model), stratopause 50, Karman 100, station 35786. - The camera's altitude at a normalised climb t in [0, 1] is the ease in `design.md`, and labels appear when the camera is within 2% of a table height. - The tether is drawn as a line from 0 to 35786 km, not to scale in the last segment, with a break mark as in `design.md`. Accept when: at the documented t values the camera altitude matches the table within 1 km, and each label is present in the listed window. ### R2. Frames - Goldens at ground (t = 0), tropopause, a stratosphere mid-point, and the station. - Facts, if on, match the text in `fixtures/elevator-facts.json`. Accept when: the four frames match the goldens, including the fact text when the option is on. ### R3. Files - One command runs the height tests and writes the frames. No network. Accept when: the command passes in both unit labels. ### 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 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. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to ride, how to read the scales, and how to run the checks.
-
design.mdThe altitude table, the climb ease, and the three-plus-one golden stops.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 * tkm (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 arefixtures/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 titleTitle A ride to orbit Shown on the ground frame. anchor_latAnchor latitude, degrees 0 From -35 to 35. The default is on the equator. factsShow altitude facts on A caption at each documented height. atmosphereShow the atmosphere bands on A colour wash for troposphere, stratosphere and above. unitsAltitude 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.mdA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/elevator-facts.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/elevator-heights.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/ride.pngThe climber at 18 400 km on the tether, Earth below. 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.
- 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.
# 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.
-
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. - The height table (R1). Build what
R1. The height tableasks for, to the numbers indesign.md. In particular: Heights in kilometres above mean sea level: ground 0, tropopause 17 (at the equator in this model), stratopause 50, Karman 100, station 35786. Check: theR1. The height tableacceptance checks pass. - Frames (R2). Build what
R2. Framesasks for, to the numbers indesign.md. In particular: Goldens at ground (t = 0), tropopause, a stratosphere mid-point, and the station. Check: theR2. Framesacceptance checks pass. - Files (R3). Build what
R3. Filesasks for, to the numbers indesign.md. In particular: One command runs the height tests and writes the frames. No network. Check: theR3. 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. **The height table (R1).** Build what `R1. The height table` asks for, to the numbers in `design.md`. In particular: Heights in kilometres above mean sea level: ground 0, tropopause 17 (at the equator in this model), stratopause 50, Karman 100, station 35786. Check: the `R1. The height table` acceptance checks pass. 3. **Frames (R2).** Build what `R2. Frames` asks for, to the numbers in `design.md`. In particular: Goldens at ground (t = 0), tropopause, a stratosphere mid-point, and the station. Check: the `R2. Frames` acceptance checks pass. 4. **Files (R3).** Build what `R3. Files` asks for, to the numbers in `design.md`. In particular: One command runs the height tests and writes the frames. No network. Check: the `R3. 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
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.