{
  "title": "Baked goods retailer package proof and ingredient version data for AI",
  "source_page": "https://fiund.com/industries/bakery-package-label-run-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A familiar bakery product name does not verify the current label revision",
    "context": "Two original ingredient-sheet covers and empty packaging props use abstract fields only. No actual recipe, food, allergen decision or production run is represented.",
    "records": [
      [
        "BL1",
        "Current practice sheet",
        "Fictional product P, revision R2, effective for mock run J2. R2 explicitly replaces R1; abstract statement code S2."
      ],
      [
        "BL2",
        "Prior proof",
        "Package proof A says P/R1/S1. Product name matches, but its readable revision is superseded for J2."
      ],
      [
        "BL3",
        "Updated proof",
        "Package proof B says P/R2/S2 with readable run J2 reference. No actual safety, compliance or release review supplied."
      ]
    ],
    "question": "Which proof matches the named practice run and revision, and what does that match leave outside the exercise?",
    "answer": "BL1 and BL3 match proof B to P/R2/S2 and run J2. BL2's matching product name does not override its superseded R1 and S1 fields. The result supports a narrow document-version match, not ingredient verification, allergen safety, legal label approval or release of actual food. Keep the observed proof revision and missing professional review separate rather than treat a readable matching code as sufficient for real use.",
    "failureModes": [
      "Choosing a familiar product name despite a superseded proof revision.",
      "Turning a revision match into a real ingredient, allergen or release determination."
    ],
    "fields": [
      [
        "Product, run and approved revision",
        "Defines the target."
      ],
      [
        "Observed proof and statement code",
        "Supports the match."
      ],
      [
        "Effective scope and professional review state",
        "Limits the result."
      ]
    ],
    "holdout": "Make proof B's code unreadable while retaining its name. Require revision verification to become unresolved rather than infer it from artwork.",
    "boundary": "Use original copy and empty packaging. Exclude recipes, vendor sheets and customer orders; qualified staff retain food and label decisions."
  }
}