[Help wanted] Carrier-specific MCT overrides & interline reality for Connection Builder

[telivity-otaip]

Who this is for

OTA shopping / schedule builders, airline schedule planners, and TMC people who know Minimum Connection Time is not "90 minutes international" everywhere. Hub specialists (ATL, DXB, LHR, SIN, CDG, ORD, …) especially welcome.

Why this hardens the system

Agent 1.x Connection Builder currently uses IATA-ish defaults + a small hub table, with open TODOs:

• Carrier-specific MCT overrides
• Real interline agreement database
• Domestic/international classification from country data

File: packages/agents/search/src/connection-builder/mct-data.ts

Wrong MCT = illegal connections sold to customers, or good connections filtered out.

What we need

1. Curated carrier@airport MCT overrides you trust (public/IATA MCT extract or operationally validated).
2. Guidance on modeling hierarchy we already sketch (carrier → airport+terminal → airport → IATA default).
3. Clarification: when is online vs interline MCT applied in your stack?
4. A starter JSON/YAML dataset under data/reference/mct/ (loader already anticipated in comments).
5. Tests that prefer carrier-specific rows over globals.

Acceptance criteria

• Documented hierarchy + at least one real hub with carrier overrides
• Dataset format agreed and checked in (even if incomplete)
• Tests covering override precedence
• Clear DOMAIN_QUESTION left for unpublished carrier exceptions — do not invent

Search keywords

help wanted · MCT · minimum connection time · interline · online connection · OTA · schedule · hub

How to contribute

Comment with airport + carrier pairs you can validate. Small PRs with a few high-traffic hubs beat a fake global table.