{
  "title": "Soap and detergent data for AI ingredient and product evidence",
  "source_page": "https://fiund.com/industries/detergent-ingredient-product-scope-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Supplier declaration names a component, not every finished variant",
    "context": "A fictional declaration references neutral input cards. No real ingredients or claims appear.",
    "records": [
      [
        "1",
        "Declaration",
        "Supplier statement applies to component J9, revision C."
      ],
      [
        "2",
        "Variant map",
        "V1 uses J9/C; V2 uses J9/D."
      ],
      [
        "3",
        "Artwork proof",
        "V2 artwork cites the supplier statement as support."
      ]
    ],
    "question": "What coverage gap should the reviewer flag?",
    "answer": "The statement covers J9/C under record 1, while V2 uses J9/D under record 2. Record 3 therefore lacks a matching component revision. Even V1's exact component match would not by itself substantiate an assertion about all of the finished product's ingredients.",
    "failureModes": [
      "Applying supplier evidence to another component revision",
      "Extending one input's scope to the whole formulation"
    ],
    "fields": [
      [
        "component_revision",
        "Joins evidence to the correct input"
      ],
      [
        "finished_variant",
        "Keeps SKU applicability explicit"
      ],
      [
        "claim_scope",
        "Separates input and finished-product statements"
      ]
    ],
    "holdout": "Use a supplier statement expressly covering a revision range and require checking both the range and claimed attribute.",
    "boundary": "No real ingredients, formula information, health claims or labeling advice."
  }
}