INDUSTRY FIELD GUIDE
Swine group handoff records for AI traceability
A group can split between destinations while the shipping file still shows one batch.
NAICS 112210 · Hog and Pig Farming
A group can split between destinations while the shipping file still shows one batch. APHIS’s swine identification and premises resources explain why source records and identifiers matter. A fictional exercise can test a model’s ability to follow the group split while preserving gaps. APHIS swine identification · APHIS premises identifier overview
Create one invented outgoing group, two dispatch records, and a single confirmed receiving record. Include number of animals and time range, with a near-match from a different exercise. Ask the assistant which branch can be verified and which proof is still required. Make a second case with a correction to the count but no correction to the destination. Label the two facts separately.
Remove true premises numbers, veterinary material, company routes, and staff identities. Do not arrange filming that changes a biosecurity practice. A documented mock handoff keeps the task about record relationships.
Describe a livestock handoff sample
Original Fiund exercise
A count correction can preserve a destination while receipt stays unconfirmed
An invented outgoing group splits between abstract destinations. Invalid aliases and arbitrary counts replace all premises, animal, company and shipment data.
| Record | Source | What it 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 for the model
Which branch has a verified receiving handoff, and what count, destination and completion state are supported for B?
Show the reference answer and checks
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.
- 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 to preserve
- 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.
Test another case
Add a DB receipt for seven with an explicit B reference. Require B's receipt status to resolve while the original plan remains historical.
Use original mock records. Exclude premises, health, routes and staff; no filming or handling that changes biosecurity practices is needed.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.