{
  "title": "Meat processing data for AI rework and lot-boundary checks",
  "source_page": "https://fiund.com/industries/meat-rework-cleaning-boundary-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Known carryover origin is not proof of addition during a stated production interval",
    "context": "An original meat-record simulation uses abstract materials and arbitrary time windows. No food, sanitation procedure, real lot definition, operating instruction or release action is supplied.",
    "records": [
      [
        "MCB1",
        "Practice boundary",
        "Exercise interval W starts after reviewed cleanup event C1 and ends before C2. Input A receipt explicitly linked to a recorded W addition."
      ],
      [
        "MCB2",
        "Rework source",
        "Tote T has documented parent lot B. Inventory lists T available during W, but addition timestamp and mixer/run link absent."
      ],
      [
        "MCB3",
        "Outside interval",
        "Input C added after C2 to another run. Similar finished-lot code, no W relationship. Original practice rule counts only linked additions within W."
      ]
    ],
    "question": "Which input is supported for W, and does T's known parent or the outside-interval entry establish another contribution?",
    "answer": "MCB1 supports A's documented addition within the stated W boundary. MCB2 proves T's B ancestry and availability, but without addition time or run link it cannot establish B contribution to W. MCB3 is outside the interval under the original exercise rule. Report A and the unresolved carryover question rather than treat storage as use or apply this fictional boundary as a real regulatory lot definition, cleanup instruction or safety decision.",
    "failureModes": [
      "Treating known rework origin or availability as confirmed use in the target interval.",
      "Applying another interval's addition to W or replacing the stated practice boundary with an assumed one."
    ],
    "fields": [
      [
        "Interval and boundary event",
        "Defines the exercise scope."
      ],
      [
        "Receipt and actual addition link",
        "Supports source inclusion."
      ],
      [
        "Rework parent and missing event time",
        "Separates ancestry from use."
      ]
    ],
    "holdout": "Add a T addition explicitly timestamped within W in a different date format. Require B to enter the supported set through the new link, not a name match.",
    "boundary": "Use wholly fabricated records and no process instructions. Exclude supplier, customer and operating data; qualified staff retain all product decisions."
  }
}