{
  "title": "Flight training simulator debrief data for AI",
  "source_page": "https://fiund.com/industries/flight-training-simulator-debrief-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Align the debrief to the run-specific event marker",
    "context": "An entirely artificial simulator record names abstract scenarios without aircraft procedures. It tests run identity and time alignment, not flight instruction or pilot readiness.",
    "records": [
      [
        "FT1",
        "Invented run SIM-A",
        "Scenario Cloud, marker M4 at elapsed 03:10."
      ],
      [
        "FT2",
        "Verified instructor debrief",
        "Names SIM-A, Cloud, M4 at 03:10; records fictional observation Z."
      ],
      [
        "FT3",
        "Invented run SIM-A2 folder",
        "Scenario Horizon, marker M4 at 01:20. Attached note repeats SIM-A / 03:10 and has no SIM-A2 amendment."
      ]
    ],
    "question": "Which run supports observation Z, and does the similarly named SIM-A2 folder provide a verified debrief for its M4 event?",
    "answer": "FT2 explicitly supports Z for SIM-A's Cloud marker M4 at 03:10, matching FT1. FT3's SIM-A2 run has a different scenario and marker time. The attachment still names SIM-A, so folder placement and the similar run name do not establish a SIM-A2 debrief. Flag the mismatched run, scenario and time for instructor review without transferring Z or making any readiness judgment.",
    "failureModes": [
      "Matching SIM-A and SIM-A2 by a common name prefix.",
      "Treating marker M4 as globally unique while ignoring scenario and elapsed time."
    ],
    "fields": [
      [
        "Exact run and scenario",
        "Disambiguates similar session names."
      ],
      [
        "Marker and elapsed time",
        "Locates the event inside the correct run."
      ],
      [
        "Debrief attribution and amendment",
        "Preserves which source an instructor actually verified."
      ]
    ],
    "holdout": "Provide an authorized SIM-A2 debrief with M4 at 01:20 but a different observation. Require separate answers for the two runs rather than merging them into one event.",
    "boundary": "Use isolated synthetic records. Include no real tracks, aircraft information, trainee records, facility controls or operating instructions."
  }
}