{
  "title": "Railroad interchange records for AI custody checks",
  "source_page": "https://fiund.com/industries/railroad-interchange-custody-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A transfer list expresses intent until an exact receiving event confirms custody",
    "context": "Two invalid training car aliases and fictional operator roles form a custody exercise. There is no actual railroad, track layout, waybill, customer or route.",
    "records": [
      [
        "RIC1",
        "Planned interchange",
        "Sending operator A lists cars DEMO-C1 and DEMO-C2 for receiving operator B at practice time T."
      ],
      [
        "RIC2",
        "Verified receipt",
        "B explicitly acknowledges DEMO-C1 at T1. Later sender correction changes C1's administrative description, not identity or receiving role."
      ],
      [
        "RIC3",
        "Second car evidence",
        "C2 has planned transfer only. Similar car C2X has a B receipt in another exercise; no C2 receipt or equivalence record."
      ]
    ],
    "question": "Which car has a confirmed custody change, and do the sender correction or near-match close C2's handoff?",
    "answer": "RIC2 explicitly confirms B's receipt of DEMO-C1, closing that fictional handoff from RIC1's plan. Its description correction preserves the same car and does not create another custody event. RIC3 leaves C2's receiving evidence absent; C2X belongs to another identity and exercise. Report C1's confirmed change and C2's planned-only state rather than treat presence in both systems or a transfer list as proof of completed interchange.",
    "failureModes": [
      "Treating a planned transfer list as a receiving acknowledgment.",
      "Using another car's near-match receipt or counting a description correction as a second handoff."
    ],
    "fields": [
      [
        "Car and sending/receiving role",
        "Defines the custody scope."
      ],
      [
        "Planned versus received event",
        "Separates stages."
      ],
      [
        "Correction target and unmatched receipt",
        "Preserves identity."
      ]
    ],
    "holdout": "Add a C2 receipt from operator C rather than B. Require the documented recipient to be reported and the intended-B mismatch flagged.",
    "boundary": "Use original fictional events. Exclude real car numbers, customers and yard details; both operators' rights govern real interchange data."
  }
}