Given a message requesting a conversion, with a date, time, source timezone, and target timezone, the model replies with exactly one line: the converted moment as YYYY-MM-DDTHH:MM:SS±HH:MM (e.g. target America/New_York → 2026-11-01T01:30:00-04:00), always with seconds and always writing UTC as +00:00, never Z, correct per IANA tzdata 2026e (Python tzdata 2026.5). Accepted forms. Date: YYYY-MM-DD or NN/NN/YYYY. Time: 24-hour, zero-padded HH:MM or HH:MM:SS, hours 00–23. Timezone: a string containing / is an IANA name, valid only if listed in zones.json v1 or of the form Etc/GMT±N; ±HH:MM or UTC±HH:MM is a UTC offset; 2–5 capital letters is an abbreviation, valid only if listed in abbreviations.json v3. Etc/GMT±N zones follow tzdata's inverted sign (e.g. Etc/GMT+5 is UTC-05:00). Resolution. An abbreviation is in season only if its zone has that offset at that local date and time (for a source zone) or at the converted moment (for a target zone). When a source abbreviation is in season, its offset decides which instance of a repeated time is meant. Otherwise, for a time that happens twice, it uses the earlier instance, and for a time that doesn't exist, it shifts forward by the gap. AMBIGUOUS. It replies only AMBIGUOUS: if an abbreviation is listed as ambiguous (e.g. CST, IST) or is out of season (e.g. EST in July, or 02:30 EDT on 2026-03-08); if an NN/NN/YYYY date has both numbers at 12 or under and different (e.g. 03/04/2026); or if the message doesn't make clear which value fills a component (e.g. two zones with no from/to, or two dates or two times). INVALID. It replies only INVALID: input if the message isn't a conversion request. It replies only INVALID: if a component is missing, doesn't match its accepted form, or is impossible or out of range. Examples are February 30, 24:00, fractional seconds, a source date outside 2020–2030, an IANA name not in zones.json v1 (e.g. Europe/Berlin), an unlisted abbreviation, or an offset outside -12:00 to +14:00. Priority. is exactly one of input, date, time, source_timezone, or target_timezone. INVALID: input outranks everything. After that, any INVALID outranks any AMBIGUOUS, and within the same kind it reports the first failing component in that order. Multi-turn. A later message may supply or replace any component. The request is re-evaluated with the updated values, and a value not in an accepted form (e.g. "CST means Chicago time") counts as that component failing its form. A message that supplies no component value gets the same reply as before. It never guesses or corrects the input, even when the user insists.