{
  "title": "Gas distribution service status records for AI",
  "source_page": "https://fiund.com/industries/gas-distribution-service-status-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Read a retrospective service note without inventing completion",
    "context": "A paper-only exercise uses invented service aliases and statuses. It contains no gas pressure, emergency instruction, system access or real customer information.",
    "records": [
      [
        "WORK-A17",
        "Scheduled practice work",
        "Alias A17 has a follow-up scheduled for day 5. The record has no completed event."
      ],
      [
        "MESSAGE-A17",
        "Reported status",
        "An unverified day-4 message says the follow-up may already be finished."
      ],
      [
        "VERIFY-A71",
        "Verified different case",
        "An authorized reviewer confirms completion for A71 on day 4."
      ],
      [
        "VERIFY-A17",
        "Later verified record",
        "A17's follow-up is recorded complete on day 6."
      ]
    ],
    "question": "What does the packet establish for A17 as of day 5, and what later event changes the documented status?",
    "answer": "By day 5, A17 has a schedule and an unverified message, without a supplied completed event. A71's confirmation concerns a different alias. VERIFY-A17 supplies A17's later documented completion on day 6. Keep the earlier uncertainty and later confirmation distinct; neither record provides an operational service-state or safety determination.",
    "failureModes": [
      "Using the similar A71 identifier as A17's completion.",
      "Promoting a schedule or unverified message into a completed event.",
      "Applying the day-6 confirmation to an earlier information cutoff."
    ],
    "fields": [
      [
        "Case identifier",
        "Preserve exact matching across messages and confirmations."
      ],
      [
        "Event status",
        "Separate scheduled, reported and verified information."
      ],
      [
        "Available-at date",
        "Identify when the completion evidence actually appears."
      ]
    ],
    "holdout": "Remove the verified A17 record and retain the rumor. The reference should remain unresolved even if several messages repeat the same claim.",
    "boundary": "Use wholly fictional retrospective records. Exclude real customers, maps, active work, configurations, pressures, credentials and emergency-response content."
  }
}