{
  "title": "Local freight delivery records for AI exception review",
  "source_page": "https://fiund.com/industries/local-freight-delivery-exception-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A stop timestamp does not mean every handling unit was accepted",
    "context": "An original local-delivery fixture uses invented stops, quantities and unit aliases. It contains no address, photograph, person, signature, rate or route.",
    "records": [
      [
        "LDX1",
        "Stop manifest",
        "Stop S, handling units A, B and C under shipment H. Generic arrival/delivery timestamp 10:00."
      ],
      [
        "LDX2",
        "Customer acknowledgment",
        "Original mock record explicitly accepts H/A and H/B; C refused with reason code REVIEW. No completed C resolution supplied."
      ],
      [
        "LDX3",
        "Later correction",
        "Corrects stop S contact-role spelling only. Explicitly leaves handling-unit acceptance and C exception unchanged."
      ]
    ],
    "question": "Which units are accepted, and do the generic timestamp or later correction resolve C?",
    "answer": "LDX2 explicitly supports acceptance of A and B and a refusal requiring review for C. LDX1's generic stop timestamp does not override that unit-level exception. LDX3 changes an administrative spelling field and expressly preserves the acceptance states. Report two accepted units and C's unresolved disposition, identifying the need for a matching resolution or new acknowledgment rather than describing the entire shipment as accepted.",
    "failureModes": [
      "Treating a stop-level delivery timestamp as acceptance of every unit.",
      "Promoting an unrelated administrative correction into resolution of a quantity or refusal exception."
    ],
    "fields": [
      [
        "Stop, shipment and handling unit",
        "Defines event scope."
      ],
      [
        "Accepted/refused state and acknowledgment",
        "Supports unit-level status."
      ],
      [
        "Correction scope and missing resolution",
        "Preserves the exception."
      ]
    ],
    "holdout": "Add a corrected acknowledgment accepting C but referencing another stop. Require the stop mismatch to remain before closing S's exception.",
    "boundary": "Use original fictional records. Exclude customer details and proof-of-delivery media; carrier, shipper and consignee rights require separate review."
  }
}