[Help wanted] GDS vs NDC routing must be per-transaction — need a real capability matrix

[telivity-otaip]

Who this is for

OTA distribution engineers and airline NDC product folks who've learned the hard way that "Airline X supports NDC" ≠ route everything to NDC. Especially valuable if you maintain a channel capability spreadsheet today.

Why this hardens the system

Agent 3.1 GDS/NDC Router is the booking channel brain. Per CLAUDE.md, routing must be per transaction type (shop / book / change / refund / groups / corporate / post-booking), not a single airline→channel map. NDC version choice is also non-portable across carriers.

See:

• docs/agents/stage-3-booking.md (Agent 3.1)
• Adapter docs under docs/adapters/ (Duffel, Sabre, Amadeus, Navitaire, TripPro)
• CLAUDE.md → Agent 3.1 guards

What we need

1. A capability matrix template columns like:
   • carrier
   • transaction (Shop, OrderCreate, OrderChange, OrderCancel, Servicing, Groups, Corporate/private fare, …)
   • channel (NDC, GDS, Direct/API, Either)
   • NDC version / profile notes
   • fallback rule
2. 3–5 anonymized carrier rows filled from your experience (public info OK).
3. Codeshare / plating notes: when marketing vs operating channel wins.
4. Guidance for when GDS remains mandatory even for "NDC airlines".

Acceptance criteria

• Matrix living in docs/knowledge-base/ (markdown or CSV)
• Explicit "per-transaction, not per-airline" rule stated
• At least one carrier where shop≠servicing channel
• Proposed input fields for Agent 3.1 to consume the matrix
• No version defaulting like "everyone is 21.3"

Search keywords

help wanted · NDC · GDS · OrderCreate · OrderChange · distribution · codeshare · OTA · capability matrix

How to contribute

Drop a redacted matrix screenshot/CSV in comments, or PR the KB template with a few example rows.