# Timezone meet ## What this builds A table that compares a proposed meeting time across a few time zones. Conversions use a shipped timezone database (or the platform's, pinned in tests) and are checked against DST fixtures, not against a live 'now' alone. A golden comparison view is taken. This is a meeting helper, not a calendar product. Read `spekkr.inputs.json` first. `title` labels the table. `home` is the first zone. `zones` chooses the list. `week` and `dst_note` change the view. The proposed instant is an input on the page; tests inject it. ## Out of scope - A live calendar or a mail-merge into a real invite, in this version. - Network or an account. - A claim of legal working-hours advice. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Conversions and DST - The fixture instants in `fixtures/tz-cases.json` (including at least one spring-forward and one fall-back in a listed zone) convert to the documented local times and offsets in every listed zone. - A proposed time of `2026-03-08T12:00:00Z` (or the file's spring case) shows the DST mark on the zone that changes that week, if `dst_note` is on. - An invalid IANA name in `home` is refused before the table renders. Accept when: every conversion case matches, the DST mark appears on the listed day, and a bad home zone is refused. ### R2. Frames and files - Goldens: a day table, a week grid, a DST mark, and a suggested overlap (a highlighted hour that is inside a documented 09:00–18:00 local window in every zone, if one exists; otherwise a 'no overlap' state). - One command runs the cases, the mark, the refusal, and writes the frames. No network. The clock is the fixture instant, not wall time. Accept when: the command passes for both zone sets, 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 Conversion tests cover DST fixtures (spring-forward, fall-back, and a no-DST zone) against a file of civil times and offsets. A golden comparison view is taken. The proposed instant is injected, not wall-clock 'now'. No network and no calendar account. ## 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 zone, how to pin an instant, and how to run the checks.