{
  "title": "Farm crew work-order records for AI evaluation",
  "source_page": "https://fiund.com/industries/farm-crew-work-order-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An approved reassignment changes the target order, while completion needs its own record",
    "context": "A fictional schedule uses crew roles and abstract sites. It is a work-order matching exercise with no actual employees, payroll or employment decisions.",
    "records": [
      [
        "FC1",
        "Original schedule",
        "Crew A assigned client X order 100 at site North; Crew B assigned X order 101 at site South."
      ],
      [
        "FC2",
        "Approved reassignment",
        "Crew A moved to X/101 at South. X/100 remains open. Crew B's assignment canceled under the original mock revision."
      ],
      [
        "FC3",
        "Completion cards",
        "Confirmed completion names Crew A and X/101 at South. Separate client Y order 100 is complete, with no X relationship."
      ]
    ],
    "question": "Which client-X order has confirmed completion, and can client Y's similar order number close the remaining X order?",
    "answer": "FC2 and FC3 support Crew A's completed work on client X order 101 at South after reassignment. X/100 remains open in the supplied record. FC3's client Y order 100 has a different client scope and cannot close X/100. Preserve the approved assignment change and distinct completion evidence without attributing the work to an individual or using the schedule alone as proof of completion.",
    "failureModes": [
      "Recording completion against the original scheduled order after an approved reassignment.",
      "Joining work orders by number while ignoring the client namespace."
    ],
    "fields": [
      [
        "Client, order and site alias",
        "Defines the work-order identity."
      ],
      [
        "Crew role and assignment revision",
        "Records the authorized change."
      ],
      [
        "Completion reference and open status",
        "Separates plans from confirmed work."
      ]
    ],
    "holdout": "Add an unsigned completion draft for X/100. Require it to be reported as a draft while the confirmed completion state remains open.",
    "boundary": "Use invented records and role labels. Exclude identity, immigration, wage and personnel information; real structures require contractor and grower approval."
  }
}