{
  "title": "Swine group handoff records for AI traceability",
  "source_page": "https://fiund.com/industries/swine-group-handoff-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A count correction can preserve a destination while receipt stays unconfirmed",
    "context": "An invented outgoing group splits between abstract destinations. Invalid aliases and arbitrary counts replace all premises, animal, company and shipment data.",
    "records": [
      [
        "SP1",
        "Outgoing split",
        "Group G: 20 practice units, branch A planned 12 to destination DA and branch B planned 8 to DB."
      ],
      [
        "SP2",
        "Dispatch and receipt",
        "Dispatch A confirms 12 to DA; receiving acknowledgment explicitly matches A/DA. Dispatch B confirms 8 to DB but no receipt supplied."
      ],
      [
        "SP3",
        "B correction and near-match",
        "Approved B correction changes count from 8 to 7, destination DB unchanged. Separate acknowledgment names branch B-old/destination DC from another exercise."
      ]
    ],
    "question": "Which branch has a verified receiving handoff, and what count, destination and completion state are supported for B?",
    "answer": "SP2 documents A's 12-unit dispatch and matched receipt at DA. SP3 corrects B's dispatched count to seven while explicitly retaining DB, but supplies no DB receiving acknowledgment. The B-old/DC near-match is a different event and destination. Report B as dispatched with corrected count seven and receipt unconfirmed; do not infer a destination change from the correction or reconcile the original group total by inventing another movement.",
    "failureModes": [
      "Changing destination when an amendment changes count only.",
      "Treating a similar branch acknowledgment as receipt or inventing a movement to force totals to balance."
    ],
    "fields": [
      [
        "Outgoing group and split branch",
        "Defines the lineage."
      ],
      [
        "Dispatch count, destination and correction scope",
        "Preserves independently revised facts."
      ],
      [
        "Receiving reference and unmatched event",
        "Limits the confirmed handoff."
      ]
    ],
    "holdout": "Add a DB receipt for seven with an explicit B reference. Require B's receipt status to resolve while the original plan remains historical.",
    "boundary": "Use original mock records. Exclude premises, health, routes and staff; no filming or handling that changes biosecurity practices is needed."
  }
}