# 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. ## Scripts `scripts/standard.json` has 12 scenes, `scripts/short.json` has 5. Both start at `fork`. Every choice points at a scene id in the same file or at `end`. Scene `fork` (both scripts), body trimmed here: - Heading used only if `title` is empty: "A fork". - Choices: `left` "Pull the lever" → `dessert`; `right` "Leave the lever" → `email`. The remaining scenes, their exact text, and their choices are in those files. Tests read the files. A change to a next-id must be made in the file and in the path table together. ## Documented paths (standard) | Path | Steps (scene, choice) | Ends at | | --- | --- | --- | | A | (fork, left), (dessert, cake), (meeting, wait) | `recap` then `end` if `recap` is on, else `end` | | B | (fork, right), (email, archive), (folders, both) | `end` | | C | (fork, left), (dessert, pie), (meeting, run) | `end` | The short script has path S: (fork, left), (dessert, cake) → `end`. Path A asides, when `narrator` is on: | After choice | Aside shown on the next scene | | --- | --- | | left | "A decisive tug." | | cake | "Sweetness, at least." | | wait | "The trolley, and the meeting, go on without you." | ## Golden frames (path A, standard, both options on) | File | When | | --- | --- | | `first-fork` | Scene `fork`, nothing chosen yet | | `chosen-left` | Scene `dessert`, after `left` | | `escalation` | Scene `meeting` | | `recap` | The recap screen | Tolerance: each channel within 8 levels, 98% of pixels. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A small problem of tracks | Shown on the first scene. | | `player_name` | Name on the lever | Alex | Used in later scenes when the text addresses the person. | | `narrator` | Narrator asides | on | A second line under the scene that comments on the last choice. | | `recap` | End recap | on | A last screen lists every choice in the path. | | `script` | Script | standard | standard is 12 scenes long. short is 5, for a quicker run. | ## 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. | | `scripts/short.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `scripts/standard.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/tracks.png` | The trolley approaches a fork: uneaten bread one way, a violin the other. | ## 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. Each scene's choices branch to the documented next scene. Three scripted paths (and one short-script path) are walked in tests and must end where the table says. Screenshots are taken at four points on path A. There is no randomness, no network, and no scoring of answers as right or wrong.