{
  "title": "Snack food manufacturing data for AI seasoning-run review",
  "source_page": "https://fiund.com/industries/snack-seasoning-run-boundary-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A continuous base lot can cross a seasoning change without carrying the old bag proof forward",
    "context": "An original midnight-boundary fixture uses inert base, seasoning and proof codes. No actual food, formula, brand artwork, operating setting or product release is represented.",
    "records": [
      [
        "SSB1",
        "Base and run map",
        "Mock base lot B spans R1 before the defined day boundary and R2 after it. Original run IDs explicit; shared base does not determine seasoning."
      ],
      [
        "SSB2",
        "Executed additions",
        "R1 records abstract seasoning S1. R2 records S2 after changeover. Separate reviewed event links for both."
      ],
      [
        "SSB3",
        "Proof register",
        "P1 approved for R1/S1, marked withdrawn for R2. Current P2 explicitly matches R2/S2. Old P1 still physically present in the mock station."
      ]
    ],
    "question": "Which proof applies to each output, and can the shared base or visible older proof override the run boundary?",
    "answer": "SSB1 and SSB2 preserve B in both runs while distinguishing R1's S1 from R2's S2. SSB3 supports P1 for R1 only and P2 for R2; P1's physical presence does not undo its withdrawal for R2. Cite run, addition and proof status together rather than infer seasoning from base-lot continuity or select a nearby bag. The fixture establishes no actual ingredient, allergen or release decision.",
    "failureModes": [
      "Carrying an old seasoning identity into a later run because the base lot repeats.",
      "Choosing an available but withdrawn proof over the matched current record."
    ],
    "fields": [
      [
        "Run interval and base lot",
        "Separates chronology and continuity."
      ],
      [
        "Executed seasoning code",
        "Defines the relevant change."
      ],
      [
        "Proof applicability and withdrawal",
        "Supports selection."
      ]
    ],
    "holdout": "Move the changeover earlier with unfamiliar codes. Require exact executed run links rather than assume the calendar day itself controls.",
    "boundary": "Use original fictional records and bag designs. Exclude real formulas and worker imagery; qualified staff retain label and release decisions."
  }
}