{
  "title": "Inland barge lock-event data for AI evaluation",
  "source_page": "https://fiund.com/industries/inland-barge-lock-event-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Queue arrival and waiting updates do not establish completed passage",
    "context": "Two invented tow aliases and abstract lock events form an offline fixture. No schedule, shipper, operating system, infrastructure coordinate or navigation instruction is included.",
    "records": [
      [
        "IL1",
        "Tow A",
        "Full ID DEMO-A, arrival observed 08:00. Operator-confirmed passage complete 08:40, exact A event reference."
      ],
      [
        "IL2",
        "Tow A2",
        "Distinct full ID DEMO-A2, arrival observed 08:20. Planned passage 09:00; update at 08:50 says waiting."
      ],
      [
        "IL3",
        "Similar-name summary",
        "A and A2 share a short display name in the original mock interface. No completion for A2 or approved identity merge supplied."
      ]
    ],
    "question": "Which tow has a completed-passage record, and what can be stated about A2's plan and last observation?",
    "answer": "IL1 explicitly confirms A's passage completed at 08:40. IL2 supports A2's observed arrival and latest waiting update; its 09:00 planned passage is not execution evidence. IL3's shared short name does not transfer A's completion to A2. Report planned, observed and confirmed times distinctly, leaving A2's completed passage unresolved even after the planned time would have passed. The fixture makes no navigation or operational decision.",
    "failureModes": [
      "Treating a planned passage time as a completed event.",
      "Matching similar tow names instead of the full training identifier."
    ],
    "fields": [
      [
        "Tow ID and display-name scope",
        "Disambiguates records."
      ],
      [
        "Arrival, waiting and passage event",
        "Separates stages."
      ],
      [
        "Planned versus confirmed timestamp",
        "Supports the state summary."
      ]
    ],
    "holdout": "Supply A2's passage-start event without completion. Require a state advance without calling passage complete.",
    "boundary": "Use synthetic logs and original schematics. Exclude actual schedules and infrastructure details; all evaluation stays offline."
  }
}