{
  "title": "Freight brokerage exception records for training workflow assistants",
  "source_page": "https://fiund.com/industries/freight-broker-exception-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Out-of-order status messages require source authority and an as-of cutoff",
    "context": "A fictional load uses abstract windows, roles and timestamps. It includes no lane, location, driver, rate, client identity or transportation-system access.",
    "records": [
      [
        "FB1",
        "Original booking",
        "Load L, pickup window W1. Shipper-authorized instruction says any pickup-window change needs shipper confirmation."
      ],
      [
        "FB2",
        "Messages available by 10:10",
        "Carrier reports delay at 10:02, received 10:03. Automated status generated 09:55 says on time, received 10:05. Shipper requests clarification at 10:08; no new window approved."
      ],
      [
        "FB3",
        "Packet cutoff",
        "This packet contains only records available by 10:10. Any later outcome belongs in a separate reviewer archive, not the model input; no later resolution is provided here."
      ]
    ],
    "question": "As of 10:10, what evidence conflict should be surfaced and who must confirm a changed pickup window?",
    "answer": "FB2's carrier delay is newer event evidence than the stale 09:55 automated status even though the latter arrived later. Surface that conflict and the shipper's clarification request. FB1 requires shipper confirmation before changing W1, and no such approval is available by 10:10. FB3 excludes later outcomes from this packet. Route the exception for shipper review without inventing a resolution or claiming later information was known at the cutoff.",
    "failureModes": [
      "Choosing the latest-arriving message despite its older source timestamp.",
      "Using a later outcome as if known at the decision cutoff or changing a window without its required authority."
    ],
    "fields": [
      [
        "Load and current authorized window",
        "Defines the booking."
      ],
      [
        "Generated versus received time and source role",
        "Supports conflict review."
      ],
      [
        "Decision cutoff and later-history partition",
        "Prevents outcome leakage."
      ]
    ],
    "holdout": "Use a different exception where the carrier corrects an earlier erroneous delay. Require evidence authority and timestamps rather than a fixed rule that delay always wins.",
    "boundary": "Use original fictional messages and separate input/answer files. Exclude commercial records, routes and account access; buyer demand and export rights require confirmation."
  }
}