{
  "title": "Independent trucking terminal queue data for AI review",
  "source_page": "https://fiund.com/industries/trucking-terminal-queue-event-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "One tractor's earlier exit cannot close its later terminal visit",
    "context": "A fictional terminal log uses invalid tractor and appointment aliases. It contains no real facility layout, driver, customer, access token or live queue state.",
    "records": [
      [
        "TQ1",
        "Visit A",
        "Tractor DEMO-T, appointment A: queue entry 08:00, door assignment 08:10, verified exit 09:00."
      ],
      [
        "TQ2",
        "Visit B",
        "Same tractor, appointment B: new gate entry 11:00. Duplicate scan repeats identical event key B-IN; no door assignment or exit for B."
      ],
      [
        "TQ3",
        "Summary draft",
        "Draft joins by tractor only and calls B exited at 09:00. Original event references distinguish A and B."
      ]
    ],
    "question": "What stage is documented for each visit, and should the repeated B-IN scan create another visit?",
    "answer": "TQ1 documents A's queue, door assignment and exit. TQ2 documents B's later gate entry only; its repeated B-IN key is one event rather than another visit. TQ3 incorrectly carries A's earlier exit to B, creating an impossible sequence and ignoring appointment identity. Keep two visit histories under the same tractor alias and leave B's door and exit states unresolved without inferring an actual terminal condition.",
    "failureModes": [
      "Joining all events by vehicle while ignoring visit or appointment.",
      "Counting an identical scan key twice or applying an earlier exit to a later arrival."
    ],
    "fields": [
      [
        "Tractor and appointment/visit ID",
        "Defines the event scope."
      ],
      [
        "Queue, door and exit type",
        "Separates stages."
      ],
      [
        "Timestamp and unique scan key",
        "Supports ordering and deduplication."
      ]
    ],
    "holdout": "Add B's exit with no door event. Require exit to become documented while the missing door history remains explicit.",
    "boundary": "Use original synthetic events. Exclude security procedures, facilities and customer identifiers; partner-controlled records need authorization."
  }
}