Skip to content

docs(kb): GDS/NDC per-carrier×vendor×transaction capability matrix (#142) - #165

Merged
telivity-otaip merged 6 commits into
mainfrom
cursor/gds-ndc-capability-matrix-2500
Aug 24, 2026
Merged

docs(kb): GDS/NDC per-carrier×vendor×transaction capability matrix (#142)#165
telivity-otaip merged 6 commits into
mainfrom
cursor/gds-ndc-capability-matrix-2500

Conversation

@telivity-otaip

@telivity-otaip telivity-otaip commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

What does this PR do?

Closes #142. Adds an authoritative GDS/NDC capability matrix so Agent 3.1 routes by (carrier, vendor, transaction) — never a single airline→channel map.

Type of change

  • Documentation
  • Enhancement to existing agent
  • Domain logic correction

Key points

  • Res 787 is treated as the Offer/Order process standard (Shop / Order / Change), not a channel parity checklist.
  • Matrix columns: carrier, vendor, transaction (Shop, OrderCreate, OrderChange, OrderCancel, Servicing, Groups, Corporate), channel, NDC version notes, fallback, source, confidence.
  • Sabre Offer/Order REST surface cited from https://developer.sabre.com/guide/ndc/ndc.html (vendor API list ≠ per-carrier enablement).
  • Seed rows are anonymized and grounded in public adapter docs; shop ≠ servicing for ANON-NDC-AGG (Duffel) and ANON-AGG-DUAL (TripPro).
  • No invented 21.3 — unknown stays unknown; NDC format stub no longer defaults to 21.3.
  • Proposed Agent 3.1 inputs: vendor, plating_carrier, capability_matrix, plus existing transaction_type / overrides. Loader in capability-matrix.ts.
  • Manifest regenerated so Agent 3.1 schema includes the new fields.

Domain impact

Hardens Agent 3.1 against per-airline channel rationalization (CLAUDE.md guards). Production carrier enablement for Sabre Offer/Order endpoints remains DOMAIN_QUESTION / unknown until evidenced.

Test plan

  • vitest run packages/agents/booking/src/gds-ndc-router — 60 passed (includes matrix shop≠servicing + no invented version)
  • pnpm gen:manifest --check — up to date
  • CI green on this PR
Open in Web Open in Cursor 

cursoragent and others added 2 commits August 24, 2026 08:02
)

Add authoritative KB matrix for Agent 3.1 so routing is keyed by
(carrier, vendor, transaction), not a single airline→channel map.

- Res 787 framed as Shop/Order/Change process standard (not parity)
- Sabre Offer/Order REST surface cited from public NDC guide
- Anonymized rows from adapter docs; shop≠servicing for Duffel + TripPro
- Matrix loader + router consumption; no invented NDC 21.3 defaults

Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Reflect transaction_type, vendor, plating_carrier, and capability_matrix
on Agent 3.1 schema after #142 KB matrix work.

Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
@telivity-otaip
telivity-otaip marked this pull request as ready for review August 24, 2026 08:40
Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
@cursor

cursor Bot commented Aug 24, 2026

Copy link
Copy Markdown

CI note: The first CI run failed only on pnpm gen:manifest --check (stale Agent 3.1 schema). That is fixed on HEAD (e61f3d7 + follow-up push) — transaction_type / vendor / plating_carrier / capability_matrix are in agents.manifest.json.

Subsequent agent pushes did not re-trigger Actions (token cannot re-run workflows). Please Re-run failed jobs on the first CI run, or push an empty commit from a maintainer account, so CI can validate HEAD.

Local verification already green:

  • vitest run packages/agents/booking/src/gds-ndc-router → 60 passed
  • pnpm gen:manifest --check → up to date

cursoragent and others added 3 commits August 24, 2026 09:25
Merge origin/main into cursor/gds-ndc-capability-matrix-2500. Only
conflict was generated docs/agent-map.html (both branches regenerated
the manifest). Regenerated agents.manifest.json and agent-map.html to
combine main's agent updates with GdsNdcRouter matrix input fields.

Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
Main advanced with #163 (BSP HOT multi-currency). Only conflict was
generated docs/agent-map.html; regenerated manifest to combine both sides.

Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
GdsNdcRouter contract schema requires transaction_type since per-
transaction routing landed. The Sprint A happy-path pipeline omitted it,
causing schema validation to fail at step 3.1.

Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
@telivity-otaip
telivity-otaip merged commit 9829bd4 into main Aug 24, 2026
1 check passed
@telivity-otaip
telivity-otaip deleted the cursor/gds-ndc-capability-matrix-2500 branch August 24, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

2 participants