{
  "title": "Ocean and coastal freight arrival data for AI review",
  "source_page": "https://fiund.com/industries/ocean-coastal-freight-arrival-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Vessel estimates, terminal requests and actual arrival events keep different meanings",
    "context": "An original port-call fixture uses fictional voyages and a single stated UTC basis. It contains no vessel identity, active schedule, cargo, berth instruction or navigation action.",
    "records": [
      [
        "PCO1",
        "Call A planned records",
        "Vessel estimate ETA 10:00 UTC. Terminal-requested berth window revised from W1 to W2; current requested time 10:30 UTC, revision explicitly confirmed by terminal."
      ],
      [
        "PCO2",
        "Call A actual event",
        "Original observed arrival event states 10:20 UTC. It does not state actual berth time or acceptance of the requested window."
      ],
      [
        "PCO3",
        "Call B conflict",
        "Vessel estimate 12:00 UTC and terminal request 12:30 UTC. No actual event or reconciled plan confirmation supplied."
      ]
    ],
    "question": "Which A values are forecasts, requests and observations, and can B's latest time be reported as actual arrival?",
    "answer": "PCO1's 10:00 is A's vessel estimate and 10:30 the terminal's current requested time after revision. PCO2 separately observes arrival at 10:20 without an actual berth event. These values describe different events and authorities. PCO3 supplies only an estimate and request for B, so neither is actual arrival and their difference remains a planning distinction to clarify. Do not select the latest number as a universal port-call truth or infer a delay basis not stated.",
    "failureModes": [
      "Treating a requested berth time as an observed vessel arrival.",
      "Choosing the latest source indiscriminately or comparing different event types as if identical."
    ],
    "fields": [
      [
        "Call and issuing role",
        "Defines authority."
      ],
      [
        "Estimate/request/actual event type",
        "Preserves meaning."
      ],
      [
        "UTC time, revision and missing confirmation",
        "Supports the retrospective summary."
      ]
    ],
    "holdout": "Give B's terminal request in an unspecified local time. Require time-basis clarification in addition to preserving event type.",
    "boundary": "Use original offline records. Exclude schedules, routes and communications; no output directs navigation or berth operations."
  }
}