{
  "title": "Cotton harvest module records for AI review",
  "source_page": "https://fiund.com/industries/cotton-field-module-handoff-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The planned truck and the confirmed receiving record can differ",
    "context": "An invented cotton-module timeline contains abstract field and truck aliases. No actual route, fleet ID, field boundary, schedule or commercial grade data is supplied.",
    "records": [
      [
        "CM1",
        "Module creation and plan",
        "Module M-A created from field F-A day 1. Planned pickup truck T1 day 2."
      ],
      [
        "CM2",
        "Actual handoff",
        "Day 2 pickup log names M-A and truck T2. Receiver G acknowledges M-A from T2 on day 3 with matching inert transfer reference H1."
      ],
      [
        "CM3",
        "Other module",
        "M-B field tag visible in a practice photo description. No pickup or receiving acknowledgment supplied; a classing-label field is blank."
      ]
    ],
    "question": "Which transport and receiving events are supported for M-A, and what can be said about M-B's handoff or eventual classing?",
    "answer": "CM2 documents M-A's actual pickup by T2 and later receiving acknowledgment at G under H1. CM1's T1 assignment was a plan, not the documented carrier. CM3 supports only M-B's field-tag observation, with no confirmed handoff or classing result. Keep field origin, planned movement, actual transport and downstream classing as distinct stages rather than treating a visible tag or receiving record as proof of every later event.",
    "failureModes": [
      "Reporting the planned truck instead of the actual confirmed one.",
      "Inferring a receiving or classing outcome from a field tag alone."
    ],
    "fields": [
      [
        "Module and field-origin alias",
        "Preserves the creation link."
      ],
      [
        "Planned versus actual transport",
        "Separates intended and observed events."
      ],
      [
        "Receiver acknowledgment and downstream state",
        "Limits what the handoff establishes."
      ]
    ],
    "holdout": "Add a receiving card for M-B with a conflicting transfer ID. Require reconciliation rather than acceptance based only on a matching module label.",
    "boundary": "Use synthetic logs and original labels. Exclude real boundaries, fleets, gin schedules and private grades; machine-generated export rights require review."
  }
}