{
  "title": "Passenger charter itinerary revisions for AI testing",
  "source_page": "https://fiund.com/industries/charter-flight-itinerary-revision-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Client receipt of a revised itinerary does not confirm every operator change",
    "context": "An original charter-document fixture uses invented roles and departure windows. It contains no passenger identity, aircraft assignment, airport access, flight plan or payment.",
    "records": [
      [
        "CFI1",
        "Confirmed plan V1",
        "Departure window W1 and generic service label S1. Operator confirmation explicitly references V1."
      ],
      [
        "CFI2",
        "Proposed V2 and responses",
        "V2 requests W2 and service label S2. Client acknowledges receiving V2. Operator confirms only S2 and explicitly leaves W2 pending; W1 retained meanwhile."
      ],
      [
        "CFI3",
        "Later draft V3",
        "Proposes W3, unsigned and unconfirmed. No additional operator event supplied."
      ]
    ],
    "question": "Which departure window and service-label change are currently supported, and what remains pending?",
    "answer": "CFI2 explicitly confirms only S2 while retaining CFI1's W1 pending a response on W2. The client's receipt acknowledgment is not operator acceptance of the requested window. CFI3's W3 remains an unconfirmed draft and does not replace either state. Report the partially confirmed plan with W2 unresolved rather than treat an entire revised itinerary as accepted from one party's acknowledgment or a narrow confirmation.",
    "failureModes": [
      "Treating client receipt as operator acceptance of an itinerary.",
      "Extending partial confirmation to all requested fields or selecting an unsigned latest draft."
    ],
    "fields": [
      [
        "Itinerary version and issuing role",
        "Defines source authority."
      ],
      [
        "Requested versus confirmed field",
        "Preserves partial acceptance."
      ],
      [
        "Retained window and pending response",
        "Makes the current documentary plan explicit."
      ]
    ],
    "holdout": "Add operator acceptance of W2 effective after the review cutoff. Require the earlier summary to retain W1 and mention the future change separately only when available.",
    "boundary": "Use original synthetic correspondence. Exclude actual dispatch and aircraft information; intermediary-controlled messages need independent reuse permission."
  }
}