{
  "title": "Emergency management exercise action and evidence data for AI",
  "source_page": "https://fiund.com/industries/emergency-office-exercise-action-evidence-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An improvement action can be assigned or marked done without validation evidence",
    "context": "A benign office tabletop tests receipt of a generic internal notice. All sites, roles and records are invented; the example contains no emergency scenario or response information.",
    "records": [
      [
        "EM1",
        "Practice after-action finding",
        "F1 identifies missing notice-receipt confirmation. Action A1 assigned to role Coordinator; status planned."
      ],
      [
        "EM2",
        "Second action record",
        "A2 marked completed in a tracking sheet. Validation field empty; no test result attached."
      ],
      [
        "EM3",
        "Independent exercise check",
        "Checks A1's revised mock process and records successful receipt confirmation. No record changes A2's validation field."
      ]
    ],
    "question": "Which assignment, completion and validation facts are evidenced, and can A2's completed checkbox or A1's check stand in for A2 validation?",
    "answer": "EM1 documents A1's assignment, and EM3 provides a specific validation observation for A1's revised practice process. EM2 records A2 as marked completed but supplies no validation result. Neither that checkbox nor A1's independent check validates A2. Report each action's separate evidence stages and flag the missing A2 test rather than calling all improvement actions demonstrated effective from a tracker status.",
    "failureModes": [
      "Treating administrative completion as independent validation.",
      "Using one action's test result to close another action's evidence gap."
    ],
    "fields": [
      [
        "Finding-to-action relation",
        "Keeps an improvement tied to the observed gap."
      ],
      [
        "Owner and tracker state",
        "Records assignment and claimed completion."
      ],
      [
        "Validation scope and result source",
        "Identifies what was independently tested."
      ]
    ],
    "holdout": "Add an A2 validation attempt that fails the stated receipt check. Require the model to retain claimed completion while reporting unsuccessful validation.",
    "boundary": "Use a generic fictional office task. Exclude preparedness plans, vulnerabilities, contact trees, infrastructure, response details and actual locations."
  }
}