{
  "title": "Taxi and limousine booking-change records for AI",
  "source_page": "https://fiund.com/industries/hired-car-booking-substitution-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Canceling a vehicle assignment can preserve the underlying booking",
    "context": "An original on-demand and prebooked-service fixture uses invented request aliases and abstract times. It contains no passenger, driver performance, location, accessibility need or payment data.",
    "records": [
      [
        "HB1",
        "Booking A",
        "Assignment A1 accepted, then explicitly canceled as a substitution. Original event assigns replacement A2 under the same booking A; completion C-A names A/A2."
      ],
      [
        "HB2",
        "Booking B",
        "Booking-level cancellation explicitly closes B, not merely its vehicle assignment. No completion event supplied."
      ],
      [
        "HB3",
        "Booking C",
        "Driver-role acceptance for assignment C1, no completion. Timestamps resemble A's but full booking and assignment IDs differ."
      ]
    ],
    "question": "Which booking has a documented completed service, which is canceled, and which remains accepted without completion?",
    "answer": "HB1 documents completion for A through replacement assignment A2; A1's assignment cancellation does not cancel the booking because the substitution is explicit. HB2 separately cancels booking B. HB3 supports acceptance for C/C1 without completed-service evidence. Preserve booking-level and assignment-level states rather than equate every canceled assignment with a canceled request or transfer A's completion through similar timestamps.",
    "failureModes": [
      "Treating an assignment cancellation during substitution as booking cancellation.",
      "Treating driver acceptance as completed service or joining events by time alone."
    ],
    "fields": [
      [
        "Booking and assignment ID",
        "Defines the two levels."
      ],
      [
        "Cancellation scope and replacement link",
        "Preserves substitutions."
      ],
      [
        "Accepted versus completed event",
        "Supports the final state."
      ]
    ],
    "holdout": "Add C1 cancellation with no replacement and no booking-level cancellation. Require both the canceled assignment and unresolved booking disposition to remain visible.",
    "boundary": "Use original synthetic records. Exclude precise routes, personal identifiers and platform exports; verify operator and partner rights before real reuse."
  }
}