slug: impala
provider: Impala
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Travel & Hospitality
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Bookings
  spec_file: impala-bookings-api-openapi.yml
  capability_id: BC-4020
  capability_id_l1: BC-4020
  capability_name: Reservation & Booking Management
  confidence: 0.92
  evidence: POST /bookings createBooking "Create a booking"; DELETE /bookings/{bookingId} cancelBooking
    "Cancel a booking"; PUT /bookings/{bookingId} updateBooking "Change a booking"
  reason: Full booking lifecycle — create, retrieve, amend, cancel hotel bookings — is squarely reservation
    and booking management. Covers both capture and modification sub-capabilities, so L1 only.
- tag: Hotels
  spec_file: impala-hotels-api-openapi.yml
  capability_id: BC-4000
  capability_id_l1: BC-4000
  capability_name: Travel Product & Inventory Management
  confidence: 0.72
  evidence: GET /hotels listHotels "List all hotels"; schemas hotelFullDetail, roomType, amenity, image;
    "Access all the marketing material you need to sell a room, from hotel amenities to images"
  reason: Exposes lodging product master and descriptive content (room types, amenities, imagery). Evidence
    sits between lodging product definition and content/imagery management, so only the L1 is asserted.