# Absurd trolley ## What this builds A short branching story told as a series of scenes. Each scene shows a situation, two or three labelled choices, and a still. The first scene is a simple fork in a set of tracks. Later scenes twist the premise (the lever is a dessert menu, the tracks are email folders, the trolley is late for a meeting). Every scene and every branch is written in a script file shipped with the project. The writing is original. Read `spekkr.inputs.json` first. `title` is the first heading. `player_name` is substituted wherever the script has `{name}`. `script` chooses the long or short set. `narrator` and `recap` change what is shown around the scenes. ## Out of scope - A serious ethics textbook, scoring, or a claim that a choice is correct. - User-authored scenes in the first version. - Network, accounts or a shared ending board. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Scenes - A scene has an id, a heading, a body, an image key, and two or three choices. Each choice has a label and the id of the next scene, or `end`. - The script file lists every scene. Missing next-ids are refused when the script is loaded. - {name} in any text is replaced with `player_name`. Accept when: loading each script succeeds, and a missing next-id in a fixture script is refused by name. ### R2. Branching - A choice moves to the documented next scene. There is no randomness in the path. - The first scene of `standard` and of `short` is `fork`. - A path is a list of (scene id, choice id). `design.md` lists three paths that must be followed exactly. Accept when: each documented path ends at the documented scene, and every step matches the table. ### R3. Chrome - If `narrator` is on, after the first choice a one-line aside from the chosen choice's `aside` field is shown under the next scene. - If `recap` is on, reaching `end` shows a list of every choice label in order, then a start-again control. - The first scene shows `title` as its heading, not the script's heading, for scene `fork` only. Accept when: path A with both options on shows the asides in the table and a recap of the three labels; with both off, neither appears. ### R4. Screenshots - The four frames in `design.md` are taken from path A at the named scenes. Accept when: they match the goldens within the tolerance in `design.md`. ### R5. Files - One command loads both scripts, walks the three paths, and writes the screenshots. No network. Accept when: the command passes from a clean folder. ## Verification 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. ## 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 run the checks, and how to edit a scene.