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