Private configuration

Store these settings in the traveler's private watch, never in a public skill update:

• Origin and destination station names and codes.
• Usual scheduled departure, preferred operator if any, and target arrival.
• IANA timezone, pre-departure start/end, optional in-journey start/end and cadence, late-arrival buffer or hard cutoff, weekdays to evaluate, excluded dates and first start date. Each traveler's hours belong in their private schedule, not this skill.
• Calendar account and calendar, working-location signal for office versus home, explicit leave overrides, and whether any weekday fallback is authorized.
• Notification destination and tone. Default to the existing private conversation; other recipients need authorization.
• Meaningful departure or arrival delay threshold (suggest 5 minutes), material change since the previous alert (suggest another 5 minutes), and major-disruption threshold (suggest 30 minutes).
• Optional station access time and boarding buffer, final-destination transfer time, acceptable interchanges, latest useful arrival, accessibility constraints and ticket restrictions. Leave unknown values unknown.
• Private durable checkpoint location supported by the host, recent-alert retrieval method, and handling for missing checkpoint access.

Example setup request for any traveler:

“Watch my usual train from [origin] to [destination], departing [time], on days my calendar marks me in the office. Check every [supported interval] from [start], and continue during the journey until arrival or [hard cutoff] in [timezone]. Alert me privately only to meaningful delays, cancellations, useful alternatives or changes to my arrival. Skip home and leave days. Do not change my calendar or contact anyone.”

Each traveler supplies their own settings. Do not assume their colleague's departure, office days, calendar or station access time applies to them.

Scheduling example

For a scheduler that supports standard RFC 5545 rules, the following represents six weekday checks at 07:00, 07:15, 07:30, 07:45, 08:00 and 08:15 local time. It is a syntax example, not an existing schedule or proof of platform support. Supply a future DTSTART in the configured timezone, validate the generated occurrences, and verify the saved result.

RRULE:FREQ=DAILY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=7,8;BYMINUTE=0,15,30,45;BYSECOND=0;BYSETPOS=1,2,3,4,5,6

Preserve Europe/London for UK local commuting when selected, so daylight-saving changes do not shift the morning window. Do not silently use a fixed UTC offset.