{
  "title": "Dried food manufacturing data for AI test-context review",
  "source_page": "https://fiund.com/industries/dried-food-water-activity-context-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Moisture and water activity are different fields, even on the same lot report",
    "context": "An original fictional dried-food test packet uses invented observations and abstract conditions. It contains no actual product, process settings, release threshold or food-safety advice.",
    "records": [
      [
        "DWA1",
        "Matched sample A",
        "Lot L, day 1: original report measures moisture 10 practice percent. No water-activity field on this report."
      ],
      [
        "DWA2",
        "Matched sample B",
        "Lot L, day 2: original report shows dimensionless mock water-activity value 0.50 under condition C. Sample and instrument aliases readable."
      ],
      [
        "DWA3",
        "Cropped report",
        "Water-activity field 0.45 under condition D, but sample and lot cropped. No reviewed link to L or B."
      ]
    ],
    "question": "Which source answers a day-two condition-C water-activity request for L, and can the other reports substitute?",
    "answer": "DWA2 matches lot L, day two, the requested property and condition C, supporting the stated dimensionless 0.50. DWA1 reports percent moisture on day one, which is a different property and cannot substitute. DWA3 has the right kind of field but lacks lot identity and uses another condition. Preserve each measurement context and leave unlinked values unattributed without using any fictional reading to judge actual food safety or release.",
    "failureModes": [
      "Replacing water activity with a nearby moisture percentage.",
      "Assigning a cropped report by property name while ignoring lot and test condition."
    ],
    "fields": [
      [
        "Sample, lot and date",
        "Defines applicability."
      ],
      [
        "Property, unit and test condition",
        "Separates measurements."
      ],
      [
        "Instrument/source and unresolved identity",
        "Limits the answer."
      ]
    ],
    "holdout": "Add both properties for one separately reviewed sample. Require precise requested-field retrieval rather than reject the complete packet.",
    "boundary": "Use original invented values only. Exclude real laboratory and operating data; qualified staff retain product and release decisions."
  }
}