Offset Itinerary Connection Auditor

How to use Offset Itinerary Connection Auditor

Enter legs in intended journey order and one transfer rule between each pair. Each local date-second is normalized to UTC before checking positive leg time, connection gaps and your own minimum/maximum requirements. The report preserves original timestamps and exact margin witnesses.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Enter legs in intended journey order and one transfer rule between each pair. Each local date-second is normalized to UTC before checking positive leg time, connection gaps and your own minimum/maximum requirements. The report preserves original timestamps and exact margin witnesses.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• At most 100 uniquely labeled legs and exactly one fewer connection rules. Timestamps require uppercase T/Z or explicit ±HH:mm, whole seconds and valid Gregorian local/UTC dates from 1900 through 9999. Offset profile is limited to ±14:00; −00:00, fractional seconds, leap-second tokens, unqualified local times and IANA zone names are refused. Durations use nominal civil/POSIX seconds with 86,400-second days, without leap-second adjustments.
• Transfer bounds are user-entered nonnegative seconds through 604,800, with null meaning no maximum. Place equality is exact and case-sensitive. This does not retrieve official minimum connecting times, infer terminal/airport transfers, model DST rules, check tickets/security/visas, predict delays or provide airline/legal travel approval. A passing result concerns only the supplied facts and assumptions.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.