{
  "title": "Refrigerated warehouse temperature-event data for AI evaluation",
  "source_page": "https://fiund.com/industries/refrigerated-warehouse-temperature-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A verified door event explains one transient but not another logger gap",
    "context": "A detached training-logger simulation uses an imaginary lot and practice zone. No food, health shipment, live cold room, product-release decision or actual operating test is involved.",
    "records": [
      [
        "CTM1",
        "Sensor A trace",
        "At one-minute intervals: 4, 4, 6, 4 practice degrees C. Original event log independently confirms the staged door-prop event at the 6 reading; reviewer labels that interval a simulated transient."
      ],
      [
        "CTM2",
        "Sensor B trace",
        "4, missing, 4. No independent event or maintenance record explains the missing sample. Different sensor and zone alias from A."
      ],
      [
        "CTM3",
        "Review scope",
        "A calibration card belongs to A only. Fixture has no food acceptance threshold, actual product condition or release authorization."
      ]
    ],
    "question": "Which interval has an independently linked explanation, and how should B's missing value and any release conclusion be handled?",
    "answer": "CTM1 links A's six-degree transient to its independently logged staged event and reviewer label. CTM2's missing B sample remains missing with unknown cause; A's event and calibration card do not transfer across sensors and zones. CTM3 supplies no acceptance rule or product evidence, so the packet supports neither a food-safety finding nor release. Preserve units, sample intervals and source-specific explanations without filling the gap or inferring cause from curve shape alone.",
    "failureModes": [
      "Assigning a cause from a spike pattern without independent evidence.",
      "Filling missing telemetry with zero or copying another sensor's calibration and event explanation."
    ],
    "fields": [
      [
        "Sensor, zone and lot alias",
        "Defines the trace."
      ],
      [
        "Unit, sampling interval and missingness",
        "Preserves measurement state."
      ],
      [
        "Independent event and reviewer scope",
        "Limits causal and release claims."
      ]
    ],
    "holdout": "Use a different simulated sensor where a similar spike has no event log. Require the cause to remain unknown despite the familiar shape.",
    "boundary": "Use original simulations or separately authorized training records. Exclude live systems and credentials; quality staff retain all product decisions."
  }
}