# Back of your hand ## What this builds A short quiz on a map of a town. Each round names a place. The person drops a pin. The true point is revealed, the score is a function of distance, and the next clue appears. The towns are invented fixture tilesets shipped with the project, so the checks never call a live map API. The streets and the place lists are original. Read `spekkr.inputs.json` first. `title` labels the game. `rounds` is how many places are asked. `city` chooses the tileset and the place list. `timer` and `metric` change the chrome. ## Out of scope - A live commercial map API in the checks, or real people dropped onto a real city without a fixture. - Accounts or a public leaderboard in the checks. - GPS or a device sensor. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Tiles and places - Each city is a folder of tiles and a `places.json` of named points in tile coordinates. - The map is drawn only from those tiles. A network request to a map provider is a test failure. - A game picks `rounds` places without replacement, using a seed. Seed 3 of `millstead` with 5 rounds is `fixtures/millstead-seed-3.json`. Accept when: the seed-3 list matches the file, and a hook around fetch reports zero map-provider calls during a game. ### R2. Distance and score - Distance is Euclidean in metres, from the tileset's stated metres-per-pixel. - Score for a round is `max(0, 1000 - floor(distance_m))`. A guess more than 1000 m away scores 0. - The game score is the sum. The fixture guesses in `design.md` produce the listed distances and scores. Accept when: each fixture guess matches distance to 0.5 m and score exactly, and a 1000.4 m guess scores 0. ### R3. A golden round - Round 1 of seed 3, millstead, with the fixture guess, is screenshotted at the clue, after the pin, after the reveal, and on the final score card after five rounds of the fixture tape. - If `timer` is on, the clock is injected and does not expire during the tape. Accept when: the four frames match the goldens, and the final score matches the file. ### R4. Files - One command runs the seed, fetch-hook, distance, and tape tests, and writes the screenshots. No network. Accept when: the command passes for both cities, with the timer on and off. ### R5. 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 Scoring is tested against a fixture tileset and place list. Checks hook network calls so a live map API cannot sneak in. Guessed versus actual distances match the fixture file, and a golden round is screenshotted. The clock is injected. No GPS and no commercial map key. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to play, how to add a fixture city, and how to run the checks.