# Future frontpage ## What this builds A generator that lays out a newspaper-like front page from a deck of stories. In CI the generator is a stub that places fixture copy into a documented layout, not a paid language-model API. The edition date is frozen. The page must include the dated items from the fixture and match layout goldens. The paper's name and the stories are original. Nothing is a real news claim. Read `spekkr.inputs.json` first. `title` is the masthead. `date` is the edition. `edition` chooses the copy deck. `kicker` and `web` change the layout. No paid API is used in the checks. ## Out of scope - A paid language-model API in the checks. - A live news scrape or a real masthead. - A claim that the stories happened. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Placement and dates - `fixtures/edition-a.json` lists stories, kickers, and a date. The generated page includes every headline in that file, and shows `date` on the masthead in a documented format. - A story marked `dated` includes its own date line, which must match the file. - A fetch hook fails if a known model or news host is contacted. Accept when: every headline and dated line is present, the masthead date matches, and the hook stays quiet. ### R2. Frames and files - Goldens: the print-like front, a web-density front, a close of the lead story, and a close of a dated item. - One command runs the stub, the hook, and writes the frames. No network and no paid API. Accept when: the command passes for both editions, 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 A stubbed generator plus fixture copy produces a page that matches layout goldens and includes every dated item and headline from the file. The edition date is frozen. A fetch hook fails if a paid model or a news host is contacted. No network is 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 to add a story, how the stub places them, and how to run the checks.