{
  "title": "Nut and peanut-butter production data for AI ingredient changes",
  "source_page": "https://fiund.com/industries/nut-butter-ingredient-change-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A compound ingredient's unchanged alias can hide a revised declaration",
    "context": "An original fictional ingredient-record exercise uses abstract compound and statement codes. It is not a real recipe, product, allergen determination or packaging approval.",
    "records": [
      [
        "NBC1",
        "Declaration history",
        "Internal alias MIX maps to mock declaration D1 with fields X/Y in recipe v1. Reviewed D2 adds abstract component Z under v2 while alias MIX stays unchanged."
      ],
      [
        "NBC2",
        "Execution and proofs",
        "Original run R explicitly records v2/MIX/D2. Proof P1 states X/Y; proof P2 states X/Y/Z. Both original inert codes."
      ],
      [
        "NBC3",
        "Purchase order",
        "Proposes replacement declaration D3 but no receiving or actual addition event. No approved run change from D2."
      ]
    ],
    "question": "Which proof matches the recorded declaration for R, and can the purchase order establish use of D3?",
    "answer": "NBC1 and NBC2 link executed R to D2, whose abstract X/Y/Z fields match P2 in this limited comparison. P1 lacks Z despite the shared MIX alias. NBC3 documents a proposed purchase only and supplies no receipt or execution evidence for D3. Preserve the exact declaration revision and run link rather than infer composition from the alias or order. The fixture does not make a real allergen, label approval or release decision.",
    "failureModes": [
      "Matching an internal alias without inspecting the changed compound declaration.",
      "Treating a purchase order as proof of receipt and use."
    ],
    "fields": [
      [
        "Compound alias and full declaration revision",
        "Defines source composition."
      ],
      [
        "Run and documented addition",
        "Supports execution."
      ],
      [
        "Proof version and proposed substitution",
        "Preserves review scope."
      ]
    ],
    "holdout": "Use a new compound alias with unchanged ingredients but corrected wording. Require the model to distinguish document revision from a composition change.",
    "boundary": "Use original abstract records only. Exclude actual formulations and supplier files; a qualified food reviewer retains real decisions."
  }
}