{
  "title": "Simulated natural gas pipeline event data for AI testing",
  "source_page": "https://fiund.com/industries/gas-pipeline-sensor-gap-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A display's retained value is not a current sensor observation",
    "context": "A detached dashboard simulation uses arbitrary units and abstract sensor names. It contains no actual telemetry, threshold, location, facility configuration or control instruction.",
    "records": [
      [
        "PG1",
        "Source A",
        "Sensor DEMO-A last observed 5 U at 10:00. At 10:10 display still shows 5 but last-update field remains 10:00; no new sample."
      ],
      [
        "PG2",
        "Maintenance source",
        "Original note explicitly names DEMO-A reporting interruption at 10:02. It describes reporting only, with no measured process condition."
      ],
      [
        "PG3",
        "Source B",
        "DEMO-B shows 7 U, last observed 10:05. Attached interruption note names separate scenario DEMO-C; no B-specific explanation or 10:10 observation."
      ]
    ],
    "question": "As of 10:10, which values are last-known rather than current, and what explanations can be attributed to each source?",
    "answer": "PG1's five is A's last-known 10:00 observation, not a new 10:10 reading. PG2 supports an A-specific reporting interruption without establishing the underlying process state. PG3's seven is B's 10:05 observation; the C note cannot explain B's later missing update. Report timestamps, staleness and source-specific evidence, leaving current conditions unverified. The packet supports human review only, without recommending any pipeline action.",
    "failureModes": [
      "Treating a retained display value as a fresh measurement.",
      "Applying another scenario's maintenance note or interpreting a reporting gap as a process condition."
    ],
    "fields": [
      [
        "Sensor/scenario alias",
        "Defines source scope."
      ],
      [
        "Observation time versus display time",
        "Exposes stale data."
      ],
      [
        "Maintenance target and missing update",
        "Limits explanation."
      ]
    ],
    "holdout": "Add a fresh B reading at 10:10 while A remains stale. Require the two source states to update independently.",
    "boundary": "Use original simulated values. Exclude real settings and systems; the task remains an offline evidence review."
  }
}