{
  "title": "Airport baggage transfer data for AI trace review",
  "source_page": "https://fiund.com/industries/airport-baggage-transfer-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A transfer scan does not establish loading onto the onward flight",
    "context": "An original baggage-log simulation uses invalid bag tags, fictional flights and abstract dates. It includes no passenger, real itinerary, restricted area or operational footage.",
    "records": [
      [
        "BG1",
        "Bag A history",
        "Service day D1: transfer event A-T followed by confirmed onward load A-L for flight F2, both exact bag A references."
      ],
      [
        "BG2",
        "Bag B history",
        "D1 transfer B-T names flight F2 as intended onward flight. No onward load event supplied."
      ],
      [
        "BG3",
        "Reused tag case",
        "Training bag C has a D2 load event. A D1 question references the same short tag, but no D1 load or date-equivalence record."
      ]
    ],
    "question": "Which bag has a matched D1 onward-load history, and what gaps remain for B and C?",
    "answer": "BG1 explicitly links A's D1 transfer and onward F2 load. BG2 supports B's transfer and intended flight but no confirmed load. BG3's C event occurs on D2 and cannot establish D1 loading from a reused short tag. Preserve service day, full identity and event type rather than close all histories from a transfer scan or a tag match across dates. The fixture makes no real baggage-delivery guarantee.",
    "failureModes": [
      "Treating transfer custody as proof of onward loading.",
      "Using a reused training tag's event from another service day."
    ],
    "fields": [
      [
        "Bag, service day and flight alias",
        "Defines the journey."
      ],
      [
        "Transfer versus load event",
        "Separates stages."
      ],
      [
        "Source system and missing confirmation",
        "Supports the evidence gap."
      ]
    ],
    "holdout": "Add a B load event for a different onward flight. Require loading to be reported with the itinerary mismatch preserved.",
    "boundary": "Use offline prop logs. Exclude actual tags, passengers and security details; airport, carrier and handler ownership must be reviewed for real event data."
  }
}