{
  "title": "Cloud infrastructure incident scenarios for AI evaluation",
  "source_page": "https://fiund.com/industries/cloud-infrastructure-incident-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Evaluate the incident using only evidence available at each moment",
    "context": "A paper tabletop uses invented services and a narrow escalation rule. The postmortem is withheld during timed questions so it cannot leak the final answer.",
    "records": [
      [
        "IN1",
        "Time 09:00 alert",
        "Fictional service Cedar has failed status checks. Cause unconfirmed; exercise rule requires notifying the incident lead."
      ],
      [
        "IN2",
        "Time 09:05 observation",
        "Independent check shows Cedar responds, while the synthetic monitor's clock is offset. Lead records probable monitoring issue, pending review."
      ],
      [
        "IN3",
        "Time 09:20 final review",
        "Reviewer confirms the tabletop monitor condition and closes the exercise. No production system or remediation action is involved."
      ]
    ],
    "question": "What assessment and escalation are supported at 09:00 versus 09:05, and why should the 09:20 review be hidden from the first question?",
    "answer": "At 09:00, IN1 supports failed checks with an unconfirmed cause and the stated incident-lead notification. At 09:05, IN2 adds evidence favoring a monitoring issue while leaving review pending. IN3 supplies the later confirmed exercise outcome, which was unavailable earlier. Revealing it during the first question would test recall of the outcome rather than whether the model updates a bounded assessment as evidence arrives.",
    "failureModes": [
      "Declaring the final cause at 09:00 by using future postmortem evidence.",
      "Treating probable cause at 09:05 as a completed review or authority to change systems."
    ],
    "fields": [
      [
        "Evidence-available time",
        "Defines the information boundary for each decision."
      ],
      [
        "Observation, hypothesis and confirmation",
        "Separates changing confidence from verified outcome."
      ],
      [
        "Escalation authority",
        "Keeps the response within the fictional rule."
      ]
    ],
    "holdout": "Use a new tabletop where a monitor issue and service issue coexist. Score whether the model preserves conflicting observations rather than applying the earlier final cause by analogy.",
    "boundary": "Use isolated synthetic artifacts and owned runbook text. Include no credentials, production topology, customer incidents, vulnerabilities or operating controls."
  }
}