INDUSTRY FIELD GUIDE
Poultry processing data for AI cut-up and case lineage
A poultry lot can branch into several cut-up products and packing runs.
NAICS 311615 · Poultry Processing
A poultry lot can branch into several cut-up products and packing runs. FSIS's HACCP records guidance provides a public context for product identification and dated evidence. A contributor can create an original dataset that follows those branches through document references. FSIS HACCP recordkeeping context
Draw a fictional source lot feeding two product streams and create separate case labels for each. Carry a small quantity into a later packing run with its own timestamp. Ask the assistant which cases have a supported relationship to the source lot. Add a case label containing the right date but a different line identifier, making date-only matching fail.
The annotation should retain each branch, the carryover event and the evidence for the final case association. Use a different product mix in the test set. Score omitted descendants and unsupported additions independently. A response should explain why a case is linked or unresolved, allowing a human reviewer to reconstruct the path without inspecting every record again.
The pilot can use diagrams and fabricated case labels. Real retailer brands, inspection information and customer orders need authority before sharing. Define the proposed use as lineage review and show the expert answer key. The buyer's accepted specification determines how much production history and variation would justify a larger licensing package.
Discuss this original manufacturing sample with Fiund
Original Fiund exercise
A carryover packing run adds a supported branch when its exact line and case links exist
An original branching graph uses abstract products, fictional source lots and empty case labels. There is no food, inspection finding, live production or release action.
| Record | Source | What it records |
|---|---|---|
| PCL1 | Source split | Mock source L feeds streams A and B. Line LA maps A to case K1; line LB maps B to K2, exact dated links. |
| PCL2 | Carryover | A retained portion of B explicitly transfers to later run R2, whose packing map names K3. Original timestamps and source links supplied. |
| PCL3 | Near-match label | Case K4 shares R2's date but label references line LX and source L2. No L or carryover link. |
Question for the model
Which cases have a supported path from L, and why does K4's date not add another descendant?
Show the reference answer and checks
PCL1 links K1 and K2 to L through separate A and B streams. PCL2 adds K3 through the documented B carryover into R2. PCL3 names another line and source, so its matching date does not establish L ancestry. Return all three supported branches with their exact links and exclude K4 rather than lose the later run or match by chronology. The fixture makes no real inspection, disposition or safety determination.
- Omitting a later documented carryover output from a source-lot trace.
- Using date alone to add a case with a conflicting line and source.
Fields to preserve
- Source lot and product stream
- Defines ancestry.
- Carryover and run-to-case reference
- Supports later branches.
- Line, date and conflicting label
- Limits unsupported additions.
Test another case
Use an unfamiliar product mix with two carryover cases. Require the complete supported set without carrying forward familiar case labels.
Use original diagrams and inert labels. Exclude actual orders, plant records and inspection information; authorized staff retain all decisions.
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.