{
  "title": "Beverage bottling changeover data for AI checks",
  "source_page": "https://fiund.com/industries/beverage-fill-changeover-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The first visible bottle with a matching code needs the current changeover record",
    "context": "Three empty unbranded prop bottles and original nonoperative line cards use invalid codes. No liquid, machine setting, actual process or product-release decision is included.",
    "records": [
      [
        "BFC1",
        "Approved mock setup",
        "Current run R2 requires label L and lot code NEW. Prior R1 also used label L with code OLD. Reviewed changeover card explicitly names R2/NEW."
      ],
      [
        "BFC2",
        "First two observations",
        "Bottle A at time 1 reads L/OLD. Bottle B at time 2 reads L/NEW and exactly matches the approved setup."
      ],
      [
        "BFC3",
        "Third observation",
        "Bottle C at time 3 shows L but lot code out of focus. No separate readable image or reviewed association."
      ]
    ],
    "question": "Which is the first fully matching observation, and which findings should be flagged rather than inferred from the label alone?",
    "answer": "BFC1 and BFC2 identify B at time two as the first supplied observation matching both L and NEW. A's L label matches but its OLD code conflicts with R2. BFC3 leaves C's code unreadable; proximity to B does not prove its lot. Report code reading and run reconciliation separately, requesting another view for C without treating this staged match as evidence of actual line clearance, process conformity or release.",
    "failureModes": [
      "Passing the first bottle because the shared label looks correct despite an obsolete lot code.",
      "Copying a nearby bottle's code into an unreadable view."
    ],
    "fields": [
      [
        "Current run and required code",
        "Defines the setup."
      ],
      [
        "Bottle ID, order and observed label",
        "Supports the first match."
      ],
      [
        "Visibility and mismatch reason",
        "Separates wrong from unknown."
      ]
    ],
    "holdout": "Use a new label design where the earliest readable matching code appears later. Require the sequence to follow observed evidence, not graphic familiarity.",
    "boundary": "Use empty original props and offline records. Exclude source water, recipes, brands and settings; actual product decisions remain with qualified staff."
  }
}