{
  "title": "Logging load handoff data for AI reconciliation",
  "source_page": "https://fiund.com/industries/logging-load-handoff-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A receiver ticket must match the dispatch, and volume bases must stay labeled",
    "context": "Two fictional log-load packets use abstract deck and trailer aliases. No active landing, loading, vehicle operation or actual timber sale appears.",
    "records": [
      [
        "LH1",
        "Dispatch A",
        "Deck D1, load L1, trailer T, day 2. Origin estimate 12 practice volume units, method ORIGIN."
      ],
      [
        "LH2",
        "Receiver A",
        "Explicitly acknowledges L1/T/day 2. Receiver estimate 11 units, method RECEIVER; no equivalence or conversion rule supplied."
      ],
      [
        "LH3",
        "Dispatch B and loose ticket",
        "Deck D2, load L2, trailer T, day 3. Loose receiver ticket names T/day 1, no L2 reference."
      ]
    ],
    "question": "Which receiving handoff is documented, and what can be inferred about B or the difference between A's volume estimates?",
    "answer": "LH2 matches LH1's load, trailer and dispatch day, documenting A's receiving link. LH3's reused trailer on a different day does not match L2, leaving B's receiver evidence missing. A's origin and receiver figures use separately labeled methods with no stated equivalence; report both rather than call the one-unit difference a verified loss. The exercise establishes documentary associations, not timber volume correctness or a commercial adjustment.",
    "failureModes": [
      "Matching a receiving ticket by reused trailer code while ignoring date and load.",
      "Interpreting different parties' volume estimates as directly comparable without a method basis."
    ],
    "fields": [
      [
        "Origin deck, load and dispatch day",
        "Defines the outgoing event."
      ],
      [
        "Receiver ticket and matched reference",
        "Supports the handoff."
      ],
      [
        "Volume unit and measuring method",
        "Preserves measurement meaning."
      ]
    ],
    "holdout": "Add a correct L2 receiver ticket with a different trailer code and an approved trailer-change record. Require matching through the documented change.",
    "boundary": "Use original records and inert diagrams. Exclude routes, drivers, sale IDs, prices and active plans; no filming at an operating landing is needed."
  }
}