{
  "title": "Courier return and redelivery records for AI traceability",
  "source_page": "https://fiund.com/industries/courier-return-custody-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A relabeled returned parcel remains one object, while proposed redelivery adds no custody event",
    "context": "An unbranded training parcel uses original nonfunctional labels and a wholly fictional event log. There is no address, recipient, delivery image or live dispatch.",
    "records": [
      [
        "CPR1",
        "Original dispatch and attempt",
        "Object O1, label L1 dispatched from mock depot D. Attempt marked unsuccessful, no recipient receipt."
      ],
      [
        "CPR2",
        "Return and relabel",
        "D acknowledges O1 returned. Approved original crosswalk replaces label L1 with L2 on the same O1; no second parcel created."
      ],
      [
        "CPR3",
        "Later plan",
        "Redelivery proposed for L2. No new dispatch scan or receiving event. Another object's L2-like scan has different full ID O2."
      ]
    ],
    "question": "Where is O1's custody last confirmed, how many parcels do L1 and L2 represent, and is redelivery established?",
    "answer": "CPR2 confirms O1's return to depot D and explicitly links L1 and L2 as successive labels on one object. CPR3's redelivery is only a proposal, with no later dispatch or receipt for O1; the O2 near-match cannot advance its history. Report D as the last confirmed custody point and preserve the unsuccessful attempt separately. Two labels do not imply two parcels or completed redelivery.",
    "failureModes": [
      "Counting relabeled returned items as separate parcels.",
      "Treating a redelivery proposal or another object's similar label as a new custody event."
    ],
    "fields": [
      [
        "Stable object ID and label crosswalk",
        "Preserves identity."
      ],
      [
        "Attempt, return and dispatch event types",
        "Separates stages."
      ],
      [
        "Custody acknowledgment and planned state",
        "Supports the last-confirmed location."
      ]
    ],
    "holdout": "Add an O1 dispatch under L2 with no final receipt. Require custody progression to be reported without calling it delivered.",
    "boundary": "Use original props and logs. Exclude recipients, routes, contractor IDs and private messages; partner-controlled real records require permission."
  }
}