[Help wanted] Fare construction hardening: IATA rounding, ROE ingestion, no haversine-as-TPM

[telivity-otaip]

Who this is for

Pricing / fare construction engineers at OTAs, airlines, or GDS practices who've implemented NUC / ROE / MPM-TPM / HIP-BHC-CTM for real. Issue farmers with ATPCO/IATA pricing scars especially welcome.

Why this hardens the system

Agent 2.2 Fare Construction territory is full of seductive wrong shortcuts called out in CLAUDE.md:

• banker's rounding ≠ IATA currency rounding
• hardcoded ROE goes stale immediately
• haversine ≠ TPM
• equal sector split ≠ TPM proration
• mileage system ≠ routing system

Package area: packages/agents/pricing/src/fare-construction/ (+ tax engine TODOs in tax-calculation/).

What we need

1. KB doc describing data contracts OTAIP should ingest (ROE monthly feed, IATA rounding table, TPM/MPM source) — not a pirate copy of the tables.
2. Recommendation for fail-closed behavior when ROE/TPM missing.
3. Minimal interface sketch for HIP/BHC/CTM checks without inventing comparison rules.
4. Tests that prove we refuse haversine substitutes and missing ROE rather than silently approximating.

Acceptance criteria

• KB "data dependencies" section for fare construction
• Explicit bans: no hardcoded ROE, no haversine-as-TPM, no generic banker rounding
• Fail-closed hooks or DOMAIN_QUESTION markers in code paths that would otherwise guess
• Contributor notes on licensed data sources (what to buy/subscribe)

Search keywords

help wanted · NUC · ROE · TPM · MPM · HIP · BHC · CTM · fare construction · IATA rounding · ATPCO · OTA pricing

How to contribute

Architecture/KB PRs preferred. Do not commit proprietary IATA/ATPCO datasets.