{
  "title": "Oilseed processing data for AI co-product lineage",
  "source_page": "https://fiund.com/industries/oilseed-meal-oil-lineage-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Co-product records can share an input while a tank dispatch has unresolved carryover",
    "context": "An original fictional co-product diagram uses abstract outputs and invented quantities. It contains no actual extraction setting, formula, supplier, shipment or product recommendation.",
    "records": [
      [
        "OMO1",
        "Run record",
        "Input I1 enters run R across shift boundary. Original map explicitly links meal output M1 and oil-style output O1 to R/I1."
      ],
      [
        "OMO2",
        "Dispatch links",
        "Dispatch D-M explicitly receives M1. D-O cites tank T, which has a confirmed O1 addition and a prior carryover quantity without source lot."
      ],
      [
        "OMO3",
        "Tank scope",
        "No source-resolved allocation of D-O's draw or full prior genealogy. A recent I1 receipt does not supersede the carryover history."
      ]
    ],
    "question": "Which output lots trace to I1, and can the whole D-O dispatch be attributed to that input?",
    "answer": "OMO1 links both M1 and O1 to I1 through R, independent of the shift boundary. OMO2 gives D-M a direct M1 link. D-O has a tank reference and O1 is a known tank input, but OMO3 leaves the carryover source and exact draw composition unresolved. Do not assign the entire dispatch to I1 or erase the unknown contribution because I1 was the latest receipt. Preserve the graph and its limits separately.",
    "failureModes": [
      "Losing one co-product branch when a run spans shifts.",
      "Attributing a whole tank dispatch to the newest known input while omitting unresolved carryover."
    ],
    "fields": [
      [
        "Run, input and co-product IDs",
        "Defines ancestry."
      ],
      [
        "Dispatch-to-output or tank reference",
        "Supports downstream links."
      ],
      [
        "Carryover and allocation evidence",
        "Limits composition attribution."
      ]
    ],
    "holdout": "Rename output categories and give a separate direct O1 dispatch. Require a complete direct trace for that event while the mixed tank case stays unresolved.",
    "boundary": "Use original fictional manifests. Exclude extraction settings, supplier terms and real shipments; qualified staff retain actual decisions."
  }
}
