[Help wanted] Involuntary rebook: IRROP triggers, reprotection hierarchy, EU261 applicability

[telivity-otaip]

Who this is for

Airline IRROP desks, OTA disruption teams, and TMC duty-of-care / reaccommodation specialists. If you've argued about 60 vs 90 minute triggers, alliance reprotection limits, or EU261 50% reductions — jump in.

Why this hardens the system

Agent 5.3 Involuntary Rebook models triggers, protection priority, and regulatory flags. Naïve defaults are dangerous:

• IRROP thresholds differ by carrier (and dep vs arrival delay)
• Alliance reprotection ≠ "any Star/oneworld/SkyTeam flight"
• EU261 applicability is a matrix (EU depart any carrier / EU arrive EU carrier), with time-window reductions
• US DOT IDB rules are oversale-specific with caps — not a generic delay payout

Files: packages/agents/exchange/src/involuntary-rebook/, docs/agents/stage-5-exchange.md, CLAUDE.md Agent 5.3.

What we need

1. A KB section: trigger taxonomy (time change, cancel, misconnect, equipment downgrade) with measurement point (dep/arr).
2. Reprotection hierarchy patterns you've implemented (same op carrier → marketing → alliance → interline → other), including endorsement constraints.
3. EU261 applicability checklist suitable for code (no invented compensation amounts unless citing the regulation text).
4. Fixture scenarios for Agent 5.3 that encode the above.

Acceptance criteria

• KB with applicability matrices + sources
• Explicit "do not hardcode 60 minutes as industry standard"
• At least 3 scenario fixtures (EU depart, EU arrive non-EU carrier, US IDB non-oversale)
• Unknown carrier policies left open — no guessing

Search keywords

help wanted · IRROP · involuntary · EU261 · denied boarding · reprotection · alliance · disruption · OTA · TMC

How to contribute

Comment with the carrier/alliance rules you've automated. Regulation citations welcome; private airline manuals — paraphrase, don't paste.