Space atlas

A browser atlas of planets, moons and orbits: fixture-date elements place bodies within tolerance, with golden system views.

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-atlas
Version
0.2.2
Published by
nova
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/nova/space-atlas/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?

Space atlas: heroSpace atlas: loop

What can I customize?

System home is a Sun-and-planets fixture. jupiter is a planet and its moons. Both use shipped elements, not a live service.

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.md Requirements and acceptance checks.

    Space atlas

    What this builds

    A calm atlas of a few systems: a star, planets, moons, and their orbits, in the browser. Positions come from shipped orbital elements evaluated at a fixture date, not from a live ephemeris service. The numbers are a documented two-body model, good enough for a beautiful atlas and strict enough to test. Names in the default home system may be familiar (they are the ordinary planets); the software and the views are original.

    Read spekkr.inputs.json first. title labels the first view. date is the instant of the default camera. system chooses the element set. trails and labels change the chrome.

    Out of scope

    • A live JPL or other ephemeris API in the checks.
    • Relativity, n-body perturbations, or spacecraft.
    • A complete star catalogue.

    Requirements

    Each requirement has an id. Checks name the id they cover.

    R1. Elements and positions
    • Each body has the orbital elements in its system file (a, e, i, Ω, ω, M0, epoch, period).
    • At the fixture date, the computed position, in the system's frame, is within the tolerance in design.md of the value in fixtures/atlas-positions.json.
    • A distance between two listed bodies matches the file within 0.5%.

    Accept when: every listed body in both systems is within tolerance, and the three listed distances match.

    R2. Views and files
    • Goldens: the home system, a closer inner-planet view, the jupiter system, and a body card for the third planet at the fixture date.
    • A fetch hook fails if a known ephemeris host is contacted.
    • One command runs the position tests, the hook, and writes the frames. No network.

    Accept when: the command passes, and the frames match the goldens.

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

    R4. Checks and report
    • One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them.
    • Checks do not need a network, a paid API, or physical hardware.

    Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it.

    Verification

    Orbital elements for a fixture date place each body within a documented tolerance of a shipped positions file. Distances between listed pairs are checked. Golden views of two systems are compared. Checks hook fetches so a live ephemeris API cannot sneak in.

    Definition of done

    • Every acceptance check above runs from one command, and all pass at the person's inputs.
    • A README says how to explore, how to add a system, and how to run the checks.
    # Space atlas
    
    ## What this builds
    
    A calm atlas of a few systems: a star, planets, moons, and their orbits,
    in the browser. Positions come from shipped orbital elements evaluated at
    a fixture date, not from a live ephemeris service. The numbers are a
    documented two-body model, good enough for a beautiful atlas and strict
    enough to test. Names in the default `home` system may be familiar (they
    are the ordinary planets); the software and the views are original.
    
    Read `spekkr.inputs.json` first. `title` labels the first view. `date` is
    the instant of the default camera. `system` chooses the element set.
    `trails` and `labels` change the chrome.
    
    ## Out of scope
    
    - A live JPL or other ephemeris API in the checks.
    - Relativity, n-body perturbations, or spacecraft.
    - A complete star catalogue.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Elements and positions
    
    - Each body has the orbital elements in its system file (a, e, i, Ω, ω,
      M0, epoch, period).
    - At the fixture date, the computed position, in the system's frame, is
      within the tolerance in `design.md` of the value in
      `fixtures/atlas-positions.json`.
    - A distance between two listed bodies matches the file within 0.5%.
    
    Accept when: every listed body in both systems is within tolerance, and
    the three listed distances match.
    
    ### R2. Views and files
    
    - Goldens: the home system, a closer inner-planet view, the jupiter
      system, and a body card for the third planet at the fixture date.
    - A fetch hook fails if a known ephemeris host is contacted.
    - One command runs the position tests, the hook, and writes the frames. No
      network.
    
    Accept when: the command passes, and the frames match the goldens.
    
    ### R3. 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.
    
    ### R4. Checks and report
    
    - One command runs every acceptance check at the defaults and at the
      person's inputs, including golden frames where a requirement asks for
      them.
    - Checks do not need a network, a paid API, or physical hardware.
    
    Accept when: the command passes at the defaults, and a deliberately broken
    fixture or a wrong price fails it.
    
    ## Verification
    
    Orbital elements for a fixture date place each body within a documented
    tolerance of a shipped positions file. Distances between listed pairs are
    checked. Golden views of two systems are compared. Checks hook fetches so
    a live ephemeris API cannot sneak in.
    
    ## Definition of done
    
    - Every acceptance check above runs from one command, and all pass at the
      person's inputs.
    - A README says how to explore, how to add a system, and how to run the
      checks.
    

    Open spec.md as plain text

  • design.md Shipped orbital elements, fixture-date positions, and golden system views.

    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.

    Model

    Positions are two-body Kepler positions from the shipped elements, at date. The algorithm (solve Kepler's equation, rotate into the system frame) is in design comments of the built project. The expected positions, in kilometres, and the tolerances (500 km for inner planets, 5000 km for outer, 50 km for moons) are fixtures/atlas-positions.json.

    Systems

    systems/home.json and systems/jupiter.json are the authority for elements. Epochs in those files are the same fixture date, so mean anomalies are used as given if epoch equals the date.

    Screenshot tolerance

    8 levels, 98% of pixels. Body centres in the image must also fall inside a 6 px circle of the projected fixture position.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA small atlas of orbitsShown on the first system view.
    dateFixture date2026-01-01T00:00:00ZThe instant used for the default view and for the checks.
    trailsShow orbital trailsonA faint path for one period of each body.
    labelsLabel bodiesonA name next to each body.
    systemSystemhomehome is a Sun-and-planets fixture. jupiter is a planet and its moons. Both use shipped elements, not a live service.

    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.

    FixtureRole
    design.mdA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/atlas-positions.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    systems/home.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    systems/jupiter.jsonA 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.

    FileWhat it shows
    shots/atlas.pngThe inner solar system at 2026-01-01T00:00:00Z, fixture elements.

    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. Orbital elements for a fixture date place each body within a documented tolerance of a shipped positions file. Distances between listed pairs are checked. Golden views of two systems are compared. Checks hook fetches so a live ephemeris API cannot sneak in.
    # 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.
    
    ## Model
    
    Positions are two-body Kepler positions from the shipped elements, at
    `date`. The algorithm (solve Kepler's equation, rotate into the system
    frame) is in `design` comments of the built project. The expected
    positions, in kilometres, and the tolerances (500 km for inner planets,
    5000 km for outer, 50 km for moons) are `fixtures/atlas-positions.json`.
    
    ## Systems
    
    `systems/home.json` and `systems/jupiter.json` are the authority for
    elements. Epochs in those files are the same fixture date, so mean
    anomalies are used as given if epoch equals the date.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. Body centres in the image must also fall inside a
    6 px circle of the projected fixture position.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A small atlas of orbits | Shown on the first system view. |
    | `date` | Fixture date | 2026-01-01T00:00:00Z | The instant used for the default view and for the checks. |
    | `trails` | Show orbital trails | on | A faint path for one period of each body. |
    | `labels` | Label bodies | on | A name next to each body. |
    | `system` | System | home | home is a Sun-and-planets fixture. jupiter is a planet and its moons. Both use shipped elements, not a live service. |
    
    ## 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/atlas-positions.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. |
    | `systems/home.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `systems/jupiter.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/atlas.png` | The inner solar system at 2026-01-01T00:00:00Z, fixture elements. |
    
    
    ## 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. Orbital elements for a fixture date place each body within a documented
    tolerance of a shipped positions file. Distances between listed pairs are
    checked. Golden views of two systems are compared. Checks hook fetches so
    a live ephemeris API cannot sneak in.
    

    Open design.md as plain text

  • tasks.md Build tasks in order, each with a check.

    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. Elements and positions (R1). Build what R1. Elements and positions asks for, to the numbers in design.md. In particular: Each body has the orbital elements in its system file (a, e, i, Ω, ω, M0, epoch, period). Check: the R1. Elements and positions acceptance checks pass.
    3. Views and files (R2). Build what R2. Views and files asks for, to the numbers in design.md. In particular: Goldens: the home system, a closer inner-planet view, the jupiter system, and a body card for the third planet at the fixture date. Check: the R2. Views and files acceptance checks pass.
    4. Inputs (R3). Build what R3. 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 R3. Inputs acceptance checks pass.
    5. Checks and report (R4). Build what R4. Checks and report asks for, to the numbers in design.md. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the R4. Checks and report 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.
    # 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. **Elements and positions (R1).** Build what `R1. Elements and
    positions` asks for, to the numbers in `design.md`. In particular: Each
    body has the orbital elements in its system file (a, e, i, Ω, ω, M0,
    epoch, period).
       Check: the `R1. Elements and positions` acceptance checks pass.
    
    3. **Views and files (R2).** Build what `R2. Views and files` asks for, to
    the numbers in `design.md`. In particular: Goldens: the home system, a
    closer inner-planet view, the jupiter system, and a body card for the
    third planet at the fixture date.
       Check: the `R2. Views and files` acceptance checks pass.
    
    4. **Inputs (R3).** Build what `R3. 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 `R3. Inputs` acceptance checks pass.
    
    5. **Checks and report (R4).** Build what `R4. Checks and report` asks
    for, to the numbers in `design.md`. In particular: One command runs every
    acceptance check at the defaults and at the person's inputs, including
    golden frames where a requirement asks for them.
       Check: the `R4. Checks and report` 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.
    

    Open tasks.md as plain text

  • reference/preview.html A 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.css Webfont faces for the reference preview.
  • reference/fonts/Geist.ttf Geist variable typeface for the reference preview.
  • reference/fonts/GeistMono.ttf Geist Mono variable typeface for the reference preview.
  • reference/fonts/Fraunces.ttf Fraunces variable typeface for the reference preview.
  • reference/fonts/Fraunces-Italic.ttf Fraunces 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 runner install 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.