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