# 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. ## Glider The standard glider, cells in `fixtures/glider.txt`, heading south-east. After 4 ticks it has moved (+1, +1). A blinker's three cells and both phases are `fixtures/blinker.txt`. ## Layers Inner grid 32 by 32 per outer cell. 4 inner ticks per outer tick. The zoomed-in fixture is `fixtures/life-layer1.json`: which outer cell, the inner pattern, and the expected inner state after 4 outer ticks (16 inner ticks). ## Screenshot tolerance 8 levels, 98% of pixels. Alive cells must match exactly in a grid extract; the image tolerance is for chrome. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Life inside life | Shown at the outer zoom. | | `rule` | Birth/survive rule | B3/S23 | The default is Life. Tests also run the default only, unless a second fixture says otherwise. | | `grid` | Show a faint grid | on | At zooms where a cell is at least 8 px. | | `wrap` | Wrap the outer field | off | The outermost layer is a torus if on, infinite empty if off. | | `seed_pattern` | Starting pattern | glider | A shipped pattern at the origin of layer 0. | ## 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/blinker.txt` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/glider.txt` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/life-layer1.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/life.png` | Gosper’s gun at 4×, rule B3/S23, tick 120. | ## 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. Known patterns (blinker, glider) are checked at a given tick, including the glider's +1,+1 offset after 4 steps. A nested-layer fixture is checked after a documented number of inner ticks. A golden frame is taken after N steps. No network and no live pattern database.