[Help wanted] Validate RBD / class-of-service maps for AF, EK, SQ, QF, NH (ADM bait)

[telivity-otaip]

Who this is for

Revenue accounting, fare filing, and TMC ticketing folks who know that booking class ≠ cabin and that carrier maps drift. If you've fixed an ADM caused by an outdated RBD table — you're the audience.

Why this hardens the system

Agent 0.4 Class of Service Mapper ships curated maps with open TODOs calling out validation needs for AF / EK / SQ / QF / NH, plus AA Basic Economy quirks on B.

File: packages/agents/reference/src/class-of-service-mapper/data.ts

Stale maps poison fare/class mismatch checks in ADM Prevention and fare shopping UX.

What we need

1. Validate or correct maps for those carriers against current filings (cite GDS fare display / ATPCO / airline commercial docs — not vibes).
2. Call out seasonal / route-specific exceptions you know (especially basic economy).
3. Propose a maintenance process: how often should maps be re-verified?
4. Add regression tests for the corrected rows.

Acceptance criteria

• Per-carrier notes with verification date + source
• Diff of corrected RBD→cabin mappings
• Tests for previously wrong rows
• Remaining unknowns left as NEEDS DOMAIN INPUT, not guessed

Search keywords

help wanted · RBD · booking class · class of service · ATPCO · ADM · fare basis · reference data

How to contribute

PR a focused carrier (e.g. only SQ) with sources. Small verified diffs beat giant speculative tables.