{
  "title": "Ready-mix concrete ticket records for AI document matching",
  "source_page": "https://fiund.com/industries/ready-mix-concrete-ticket-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A delivery ticket shows load identity; the field note shows arrival",
    "context": "Mock load identifiers track a fictional delivery sequence. The case includes no mix formulation, placement instructions or suitability criteria.",
    "records": [
      [
        "1",
        "Plant ticket",
        "Load L6 assigned truck T2; plant departure 10:00."
      ],
      [
        "2",
        "Gate note",
        "T2 arrived 10:35; scanned load identifier L6."
      ],
      [
        "3",
        "Order update",
        "A later reprint of L6 ticket at 10:42; no second dispatch."
      ]
    ],
    "question": "What is the documented transit interval and load count?",
    "answer": "Records 1 and 2 link one L6 delivery and show 35 minutes from departure to gate arrival. The later 10:42 reprint in record 3 is an administrative event for the same load. Do not count it as another dispatch or use it for transit time.",
    "failureModes": [
      "Counting ticket reprints as deliveries",
      "Substituting document time for movement time"
    ],
    "fields": [
      [
        "load_id",
        "Deduplicates copies and joins movement events"
      ],
      [
        "event_type",
        "Separates gate, dispatch and reprint"
      ],
      [
        "event_timestamp",
        "Supports interval calculation"
      ]
    ],
    "holdout": "Use two loads on T2 the same morning and require matching by load ID before computing intervals.",
    "boundary": "No actual mix design, site or customer data, placement windows or engineering decisions."
  }
}