{
  "title": "Bakery label and batch records for AI verification",
  "source_page": "https://fiund.com/industries/bakery-label-and-batch-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Matching proof text cannot make up for a missing lot reference",
    "context": "An original bakery packaging exercise uses empty wrappers and abstract ingredient statement codes. No actual recipe, food, allergen outcome, customer or release decision appears.",
    "records": [
      [
        "BLB1",
        "Approved mock ingredient and proof record",
        "Fictional run L2 uses ingredient statement revision S2. Approved proof P2 explicitly names L2 and S2. Older L1/P1 uses S1."
      ],
      [
        "BLB2",
        "Wrapper A observation",
        "A has readable lot L2 but visibly carries S1, the older statement code. Exact prop and photo source supplied."
      ],
      [
        "BLB3",
        "Wrapper B observation",
        "B displays S2 text code but its lot area is cropped. No verified link to L2 or another run."
      ]
    ],
    "question": "Which specific discrepancies should be routed for review, and can either wrapper be described as fully matched to P2?",
    "answer": "BLB1 supplies P2's approved L2/S2 pair. BLB2 matches L2 but conflicts on S1 versus S2. BLB3 matches the visible S2 text code but lacks a lot link, so that text match cannot establish L2 provenance. Neither wrapper verifies both fields. Send the exact version mismatch and missing lot reference to the designated reviewer separately rather than issue a generic alert or infer an actual ingredient, allergen or release outcome.",
    "failureModes": [
      "Checking label text while overlooking lot linkage.",
      "Treating a correct lot code as approval of an outdated statement or making a release decision from the exercise."
    ],
    "fields": [
      [
        "Run and approved statement/proof",
        "Defines the target pair."
      ],
      [
        "Observed text revision and lot visibility",
        "Distinguishes mismatch from missingness."
      ],
      [
        "Reviewer exception and source",
        "Makes the handoff actionable."
      ]
    ],
    "holdout": "Supply an exact L2/S2 view from a distinct mock run format. Require a clean match rather than an automatic warning for every package.",
    "boundary": "Use original empty props and abstract ingredient codes. Exclude recipes and real packaging data; qualified food staff retain release decisions."
  }
}