{
  "title": "Aircraft, rail and vessel lease return data for AI",
  "source_page": "https://fiund.com/industries/commercial-fleet-lease-return-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A return window and a condition note do not equal redelivery acceptance",
    "context": "A fictional fleet lessor uses separate practice assets and mode-specific records. The exercise interprets event states without deciding airworthiness, seaworthiness, rail serviceability or contractual compliance.",
    "records": [
      [
        "FL1",
        "Aircraft alias A practice packet",
        "Return appointment June 4; authorized lessor acknowledgment expressly accepts A on June 5 under exercise scope X."
      ],
      [
        "FL2",
        "Rail alias R practice packet",
        "Return appointment June 4; condition summary received June 5; acceptance field blank."
      ],
      [
        "FL3",
        "Vessel alias V practice rule",
        "Separate mode-specific checklist required; no V return or acceptance event supplied."
      ]
    ],
    "question": "Which asset has documented acceptance, and may the aircraft acknowledgment or rail condition summary close the other modes' return states?",
    "answer": "FL1 explicitly documents lessor acceptance for A under the stated exercise scope, separately from its appointment. FL2 documents R's planned return and received condition summary but not acceptance. FL3 establishes only a practice requirement for V. Neither A's acknowledgment nor R's condition record can be transferred across assets or modes. Keep each return state and the authorized party's evidence separate.",
    "failureModes": [
      "Treating a scheduled return or received condition summary as accepted redelivery.",
      "Applying an aircraft-specific acknowledgment or checklist to a rail or vessel alias."
    ],
    "fields": [
      [
        "Asset alias and mode",
        "Limits each record to the correct equipment context."
      ],
      [
        "Appointment, receipt and acceptance dates",
        "Separates planned and completed milestones."
      ],
      [
        "Authorized party and scope",
        "Shows what the acknowledgment actually accepts."
      ]
    ],
    "holdout": "Add a rail acceptance note limited to document receipt. Require the answer to preserve the distinction from acceptance of the asset's return.",
    "boundary": "Use invented aliases and clauses. Exclude real asset IDs, maintenance findings, locations, technical files and lease rates. No service or safety approval is produced."
  }
}