# 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. ## Level I1 (solvable) A 5 by 5 grid, rows from the top. `H` is a hopper of colour A, `h` of colour B, `O` a burrow for A, `o` for B, `B` a blocker, `.` empty. ``` H . . . O . B . . . . . . . . . . B . . o . . . h ``` The machine-checked move list is `fixtures/i1-moves.json`. Tests apply that file, not a re-typed list, to reach a solved board. The file holds seven moves and, applied in order to I1, places every hopper on its burrow. The legal movers at the start of I1 are snapshotted in `fixtures/i1-legal-start.json`. Tests compare the engine's legal set to that file. ## Position U1 (unsolvable) ``` H B O . . . B . . . . . . . . . . . . . . . . . . ``` `H` cannot pass the blockers to reach `O`, blockers cannot step onto `O`, and no other hopper exists. A search to depth 30 finds no solve. ## Packs `packs/intro.json` holds I1–I5 and U1. `packs/full.json` holds those plus I6–I15, at least three of which are marked unsolvable. Every solvable level ships with a solution file under `fixtures/`. ## Screenshot tolerance Each channel within 8 levels, 98% of pixels, on a 1600 by 1000 frame. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Two kinds of steps | Shown above the board. | | `size` | Board size | 5 | Width and height, 4 to 7. | | `hints` | Show a legal-move hint | on | A control highlights the pieces that can move now. | | `undo` | Allow undo | on | A control steps back one move, up to the start of the level. | | `pack` | Level pack | intro | intro is five levels. full is fifteen. | ## 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/i1-legal-start.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/i1-moves.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `packs/full.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `packs/intro.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/board.png` | A 5×5 mid-solve: foxes stride, hares hop, the moss still open. | ## 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. Unit tests cover hopper and blocker movement, including illegal moves off the board and through blockers. The documented I1 solution solves the level; a search agrees it is solvable in at most 7 moves. Position U1 is reported unsolvable. Golden frames are taken for a short solve and for the blocked position. No physical pieces and no network.