{
  "title": "Travel agency ticketing and itinerary status records for AI",
  "source_page": "https://fiund.com/industries/travel-agency-ticket-status-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A priced itinerary, issued ticket and refund request describe different states",
    "context": "Two imaginary itineraries use invalid booking references and original mock screens. No passenger, passport, payment token, actual ticket or booking-system export appears.",
    "records": [
      [
        "TA1",
        "Itinerary A",
        "Departure slot T, priced quote Q-A. Status QUOTED; no issued-ticket event."
      ],
      [
        "TA2",
        "Itinerary B",
        "Same departure slot T, distinct booking B. Original dummy ticket event I-B explicitly links to B and is labeled ISSUED."
      ],
      [
        "TA3",
        "Refund record",
        "Request R-B asks for a refund of I-B. No approval, settlement or completed refund event supplied; draft summary calls both itineraries ticketed and B refunded."
      ]
    ],
    "question": "Which itinerary has documented ticket issuance, and what refund state is supported for B?",
    "answer": "TA2 explicitly supports issuance for itinerary B through I-B. TA1 remains a priced quote even though its departure slot matches B's. TA3 records a refund request for I-B without approval or settlement evidence, so B's completed refund is unverified. Correct the draft's two status errors and keep quote, ticket and refund events distinct. The fixture does not determine refund entitlement or perform a booking or payment action.",
    "failureModes": [
      "Treating a priced itinerary as an issued ticket.",
      "Inferring a completed refund from a request or merging bookings by departure time."
    ],
    "fields": [
      [
        "Itinerary and invalid booking ID",
        "Defines the record."
      ],
      [
        "Quote versus issued-ticket event",
        "Separates stages."
      ],
      [
        "Refund target and settlement evidence",
        "Limits the outcome claim."
      ]
    ],
    "holdout": "Add an issued ticket for A but a refund approval only for B. Require issuance and refund states to update independently without inventing settlement.",
    "boundary": "Use original mockups and nonvalid references. Exclude passengers, histories, passports and payment credentials."
  }
}