{
  "title": "Livestock support service batch records for AI",
  "source_page": "https://fiund.com/industries/livestock-service-batch-handoff-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An administrative correction does not supply a missing service cross-reference",
    "context": "A fictional service provider and farm use inert batch aliases and original paperwork. No animal procedure, genetic material, shipment or official certificate is involved.",
    "records": [
      [
        "LS1",
        "Confirmed crosswalk",
        "Provider batch P1 maps to farm batch F1 for request R1, acknowledged by both mock record owners."
      ],
      [
        "LS2",
        "Second request",
        "Provider batch P2 references R2, farm card says F2, but no P2-to-F2 crosswalk or receiving acknowledgment supplied."
      ],
      [
        "LS3",
        "Administrative revision",
        "R2 contact-role label changed from desk A to desk B. Revision explicitly changes no batch or receiving fields."
      ]
    ],
    "question": "Which handoff can be associated across both record systems, and does R2's revision resolve its missing evidence?",
    "answer": "LS1 explicitly connects P1 and F1 under R1 with the fictional acknowledgments. LS2 lacks the cross-system link and receipt evidence for P2 and F2. LS3 revises only an administrative role label, so it cannot establish that those batches match or that a handoff occurred. Preserve the revision's scope and request the missing association rather than inferring completion from an updated record.",
    "failureModes": [
      "Treating administrative activity as proof of a completed service handoff.",
      "Joining two batch systems without an approved cross-reference."
    ],
    "fields": [
      [
        "Request and provider/farm batch aliases",
        "Defines each record namespace."
      ],
      [
        "Crosswalk authority and acknowledgment",
        "Supports the handoff relationship."
      ],
      [
        "Changed administrative field and unresolved state",
        "Limits what the revision establishes."
      ]
    ],
    "holdout": "Add an R2 crosswalk without receipt acknowledgment. Require identity matching to resolve while completion remains unconfirmed.",
    "boundary": "Use independently authored fictional cards. Exclude genetics, animal and customer records, shipments and health certificates; the exercise authorizes no service or shipment."
  }
}