{
  "title": "Prepared food manufacturing data for AI assembly and date evidence",
  "source_page": "https://fiund.com/industries/prepared-food-assembly-useby-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Receiving, assembly and stated use-by dates cannot be collapsed into one date field",
    "context": "An original prepared-kit fixture uses abstract ingredients and fictional dates. It contains no actual food, shelf-life determination, customer label or operational recipe.",
    "records": [
      [
        "PFU1",
        "Incoming components",
        "Mock component A received day 1; B received day 2. Component C held for a later run, no A1 addition event."
      ],
      [
        "PFU2",
        "Assembly sheet",
        "Output A1 assembled day 3 using documented A and B. Original sheet explicitly lists the two additions and excludes a recorded use of C."
      ],
      [
        "PFU3",
        "Finished label",
        "A1 label states use-by day 7. No derivation rule, storage assumption or authority to calculate another product's shelf life."
      ]
    ],
    "question": "Which source supports each date and component claim, and can the date difference be treated as an approved shelf-life rule?",
    "answer": "PFU1 supports A and B receipt on days one and two. PFU2 separately supports assembly on day three with A and B; C's presence under hold does not document use. PFU3 states day seven as the label's use-by field. Although four days separate assembly and that label date, no source establishes a general shelf-life rule or actual safety. Preserve event names and exact component links instead of deriving further recommendations.",
    "failureModes": [
      "Confusing a component receipt date with a finished assembly or label date.",
      "Inferring shelf life from elapsed days or adding an unused held component to output lineage."
    ],
    "fields": [
      [
        "Component, receipt and hold state",
        "Defines inputs."
      ],
      [
        "Output and assembly event",
        "Supports actual use."
      ],
      [
        "Label date type and absent derivation rule",
        "Limits time claims."
      ]
    ],
    "holdout": "Add a different finished kit with the same assembly date but a distinct stated label date. Require both to be cited without inventing a universal rule.",
    "boundary": "Use original fictional labels and records. Exclude real supplier and distribution data; qualified staff retain actual shelf-life and release decisions."
  }
}