# Invented store ## What this builds A shop that, given a search, invents a product listing: a name, a short pitch, a fake price, a picture. In CI the generator is a deterministic stub (or a template), not a paid language-model API. Fixture prompts produce a structured listing that matches a file, and a golden product page is taken. The inventedness is obvious in the copy. Nothing is for sale. Read `spekkr.inputs.json` first. `title` is the store name. `query` is the first search. `generator` chooses the stub or the template. `price` and `image` change the card. No paid API is used in the checks. ## Out of scope - A paid language-model API in the checks. - A real checkout, a real payment, or a scrape of a shop. - A claim that the product exists. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Fixture prompts - Each prompt in `fixtures/invented-prompts.json` produces a listing with the keys `name`, `pitch`, `sku`, and optional `price` and `image` alt, matching the file (the stub is deterministic). - The default query produces the listing in that file. A fetch hook fails if a known paid model or shop host is contacted. - The page says the goods are invented, in a documented line of copy. Accept when: every prompt matches the structured listing, the disclaimer line is present, and the hook stays quiet. ### R2. Frames and files - Goldens: the search box, a listing card, the default product page, and a template-generator page. - One command runs the prompts, the hook, and writes the frames. No network and no paid API. Accept when: the command passes for both generators, and the frames match the goldens. ### R3. Inputs - The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ### R4. Checks and report - One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. - Checks do not need a network, a paid API, or physical hardware. Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it. ## Verification Fixture prompts produce a structured listing from a deterministic stub or template, matching a file. A golden product page is checked. A fetch hook fails if a paid API or a shop host is contacted. No checkout and no network are required in CI. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how the stub works, how a later model hook could be added, and how to run the checks.