{
  "title": "Aircraft ground service records for AI handoff review",
  "source_page": "https://fiund.com/industries/aircraft-ground-service-confirmation-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A vendor acknowledgment does not establish turnaround-service completion",
    "context": "A simulated turnaround uses invalid flight aliases and generic task labels. It contains no aircraft details, ramp footage, procedure or release decision.",
    "records": [
      [
        "AGS1",
        "Task assignments",
        "Turnaround T1: task A reassigned from vendor V1 to V2; task B remains V3. Original change authority supplied."
      ],
      [
        "AGS2",
        "Completion and acknowledgment",
        "Authorized completion names T1/A/V2. V3 acknowledges T1/B request but gives no completion event."
      ],
      [
        "AGS3",
        "Later message",
        "V3 reports task B complete for T2, a different turnaround. Its timestamp uses a local clock without conversion to T1's reference clock."
      ]
    ],
    "question": "Which T1 task is documented complete, and why cannot the later V3 message close B or establish a precise interval?",
    "answer": "AGS1 and AGS2 support T1/A's reassignment and authorized completion by V2. T1/B has only V3's request acknowledgment. AGS3 belongs to T2 and lacks a clock conversion, so it cannot close T1/B or support a precise cross-clock interval. Preserve turnaround, task, vendor and time basis instead of treating an acknowledgment or similar later message as completion. No aircraft readiness or release conclusion follows.",
    "failureModes": [
      "Reporting a task complete from vendor acceptance alone.",
      "Matching across turnarounds or calculating elapsed time across unaligned clocks."
    ],
    "fields": [
      [
        "Turnaround, task and current vendor",
        "Defines the assignment."
      ],
      [
        "Acknowledgment versus authorized completion",
        "Separates stages."
      ],
      [
        "Source clock and event target",
        "Limits timing and association."
      ]
    ],
    "holdout": "Provide T1/B completion but leave its clock basis unknown. Require completion identity to resolve while the exact interval stays uncertain.",
    "boundary": "Use invented offline records. Exclude tail numbers, credentials, restricted procedures and live ramp material; airport and handler approval govern real records."
  }
}