Scale of life
A careful zoom from a cell to a planet, with scale math that puts a stated object at a documented stop.
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/scale-of-life- Version
- 0.2.2
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/scale-of-life/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.Scale of life
What this builds
A page that zooms, continuously, from a microscopic object to a planetary one, stopping at named scales. Each stop has a length in metres, a camera zoom, and a short label. The path is original. The feel is a thing people send to a friend, but the math is strict: a stated object is at a documented zoom and position.
Read
spekkr.inputs.jsonfirst.titleis on the first stop.pathchooses the stop list.unitsonly changes labels.labelsandcrossfadechange the chrome.Out of scope
- A 3D scan library or a copyrighted photograph set in the checks; shipped art is original or permissively licensed.
- Network, or a live zoom of a remote dataset.
- A claim of scientific authority beyond the lengths in design.md.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. The path
- Each stop has an id, a length in metres, a camera height (world units), and a label.
- The
lifepath has the twelve stops indesign.md, from a bacterium at 2e-6 m to a planet at 1.274e7 m. - Zoom between two stops is exponential in length: camera height is k * length, with k in
design.md.
Accept when: every listed object is at the documented camera height within 0.5%, and a mid-interpolation between two stops is the geometric mean of their lengths.
R2. Frames
- Golden frames are taken at the settled camera for
cell,hand,tree, andplanet(stops 0, 4, 7, 11 oflife). - The frame includes the label if
labelsis on.
Accept when: the four frames match the goldens within the tolerance in
design.md.R3. Files
- One command runs the scale math and writes the frames. No network.
Accept when: the command passes for both paths, with labels on and off.
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
Scale math tests place each stated object at a documented zoom and camera height. A mid-point between two stops is the geometric mean of their lengths. Golden frames are taken at four stops. No live dataset 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 zoom, how to add a stop, and how to run the checks.
# Scale of life ## What this builds A page that zooms, continuously, from a microscopic object to a planetary one, stopping at named scales. Each stop has a length in metres, a camera zoom, and a short label. The path is original. The feel is a thing people send to a friend, but the math is strict: a stated object is at a documented zoom and position. Read `spekkr.inputs.json` first. `title` is on the first stop. `path` chooses the stop list. `units` only changes labels. `labels` and `crossfade` change the chrome. ## Out of scope - A 3D scan library or a copyrighted photograph set in the checks; shipped art is original or permissively licensed. - Network, or a live zoom of a remote dataset. - A claim of scientific authority beyond the lengths in design.md. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. The path - Each stop has an id, a length in metres, a camera height (world units), and a label. - The `life` path has the twelve stops in `design.md`, from a bacterium at 2e-6 m to a planet at 1.274e7 m. - Zoom between two stops is exponential in length: camera height is k * length, with k in `design.md`. Accept when: every listed object is at the documented camera height within 0.5%, and a mid-interpolation between two stops is the geometric mean of their lengths. ### R2. Frames - Golden frames are taken at the settled camera for `cell`, `hand`, `tree`, and `planet` (stops 0, 4, 7, 11 of `life`). - The frame includes the label if `labels` is on. Accept when: the four frames match the goldens within the tolerance in `design.md`. ### R3. Files - One command runs the scale math and writes the frames. No network. Accept when: the command passes for both paths, with labels on and off. ### 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 Scale math tests place each stated object at a documented zoom and camera height. A mid-point between two stops is the geometric mean of their lengths. Golden frames are taken at four stops. No live dataset 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 zoom, how to add a stop, and how to run the checks.
-
design.mdThe stop list, scale math and golden camera heights.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.
Stops (
life)The exact table is
fixtures/scale-stops.json. It includes, in metres: bacterium 2e-6, cell 3e-5, grain 1e-3, finger 7e-2, hand 1.8e-1, person 1.7, room 5, tree 20, hill 200, city 2e4, country 1e6, planet 1.274e7.Camera height is
length * 3.2world units, with a world unit of 1 metre at thepersonstop. Tests compare height to 0.5%.shortis stops bacterium, hand, person, tree, planet.Screenshot tolerance
8 levels, 98% of pixels, 1600 by 1000, settled, no crossfade in motion.
Inputs
Key Label Default Notes titleTitle From a cell to a world Shown at the first stop. unitsUnit system metric Labels only. The math in design.md is in metres and always holds. labelsShow size labels on Each stop names the object and its length. crossfadeCrossfade stops on A short dissolve between two stops. Tests may take the settled frame. pathZoom path life life is the full twelve-stop path. short is five stops, for quicker checks. 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/scale-stops.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/leaf.pngThe zoom parked on a leaf, 5 cm, mid-way from a cell to a planet. 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.
- Scale math tests place each stated object at a documented zoom and camera height. A mid-point between two stops is the geometric mean of their lengths. Golden frames are taken at four stops. No live dataset 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. ## Stops (`life`) The exact table is `fixtures/scale-stops.json`. It includes, in metres: bacterium 2e-6, cell 3e-5, grain 1e-3, finger 7e-2, hand 1.8e-1, person 1.7, room 5, tree 20, hill 200, city 2e4, country 1e6, planet 1.274e7. Camera height is `length * 3.2` world units, with a world unit of 1 metre at the `person` stop. Tests compare height to 0.5%. `short` is stops bacterium, hand, person, tree, planet. ## Screenshot tolerance 8 levels, 98% of pixels, 1600 by 1000, settled, no crossfade in motion. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | From a cell to a world | Shown at the first stop. | | `units` | Unit system | metric | Labels only. The math in design.md is in metres and always holds. | | `labels` | Show size labels | on | Each stop names the object and its length. | | `crossfade` | Crossfade stops | on | A short dissolve between two stops. Tests may take the settled frame. | | `path` | Zoom path | life | life is the full twelve-stop path. short is five stops, for quicker checks. | ## 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/scale-stops.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/leaf.png` | The zoom parked on a leaf, 5 cm, mid-way from a cell to a planet. | ## 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. Scale math tests place each stated object at a documented zoom and camera height. A mid-point between two stops is the geometric mean of their lengths. Golden frames are taken at four stops. No live dataset 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 path (R1). Build what
R1. The pathasks for, to the numbers indesign.md. In particular: Each stop has an id, a length in metres, a camera height (world units), and a label. Check: theR1. The pathacceptance checks pass. - Frames (R2). Build what
R2. Framesasks for, to the numbers indesign.md. In particular: Golden frames are taken at the settled camera forcell,hand,tree, andplanet(stops 0, 4, 7, 11 oflife). Check: theR2. Framesacceptance checks pass. - Files (R3). Build what
R3. Filesasks for, to the numbers indesign.md. In particular: One command runs the scale math 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 path (R1).** Build what `R1. The path` asks for, to the numbers in `design.md`. In particular: Each stop has an id, a length in metres, a camera height (world units), and a label. Check: the `R1. The path` acceptance checks pass. 3. **Frames (R2).** Build what `R2. Frames` asks for, to the numbers in `design.md`. In particular: Golden frames are taken at the settled camera for `cell`, `hand`, `tree`, and `planet` (stops 0, 4, 7, 11 of `life`). 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 scale math 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.