# 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. ## Pipeline Height (value noise, 5 octaves) → sea level 0.42 → simple hydraulic erosion, 12 iterations, parameters in `fixtures/erosion.json` → moisture from slope and rain shadow → biome table → optional names. ## Biome table (temperate) Rows are moisture bands, columns are height bands. The table is `fixtures/biomes-temperate.json` (and arid, polar siblings). Tests look up, they do not re-derive. ## Screenshot tolerance 8 levels, 98% of pixels. The landmask hash is exact. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A land that was not there | Shown on the map margin. | | `seed` | Seed | 19 | A whole number. | | `size` | Map size | 256 | Width and height, 128, 256 or 512. | | `names` | Place names | on | A small set of generated names on coasts and hills. | | `explain` | Explain the steps | on | A side list of the pipeline steps as they run. | | `climate` | Climate | temperate | The biome table, not the height field. | ## 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/biomes-temperate.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/erosion.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/map-19-biomes.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/map.png` | Seed 19, a landmask with inked coasts, a river, and three towns. | ## 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. A seeded world is deterministic: the landmask hash matches a shipped file, and biomes at documented cells match a fixture. Golden map images are taken at four pipeline stages. Names come from a shipped lexicon, not a live model. No network.