{
  "title": "Shuttle transfer and vehicle assignment records for AI",
  "source_page": "https://fiund.com/industries/scheduled-shuttle-handoff-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A vehicle substitution stays within its dated shuttle run",
    "context": "Two invented shuttle runs share a display name but use abstract dates and vehicles. There are no guests, employees, riders, private stops or actual assignments.",
    "records": [
      [
        "SHU1",
        "Run map",
        "Run NAME on D1 initially assigned vehicle V1; same NAME on D2 assigned V3. Distinct full run IDs R1 and R2."
      ],
      [
        "SHU2",
        "R1 substitution",
        "Reviewed correction changes D1/R1 from V1 to V2. Original observed transfer event explicitly confirms R1/V2 arrival and handoff."
      ],
      [
        "SHU3",
        "Unactivated alternative",
        "Proposal would replace R2/V3 with V4, never dispatched or confirmed. No D2 transfer observation supplied."
      ]
    ],
    "question": "Which vehicle and handoff are supported for each dated run, and does the proposal or repeated name extend R1's evidence to D2?",
    "answer": "SHU2 supports D1/R1's corrected V2 assignment and observed handoff. SHU1 retains D2/R2's V3 planned assignment, while SHU3's V4 remains an unactivated proposal with no observed transfer. The repeated display name does not transfer D1's confirmation to D2. Report planned assignment, correction and observed event separately rather than claim a future run occurred or an alternate vehicle was dispatched.",
    "failureModes": [
      "Joining runs by display name while ignoring the service date.",
      "Treating a proposed replacement as dispatched or a corrected assignment as observed arrival without its event."
    ],
    "fields": [
      [
        "Full run ID and date",
        "Defines the instance."
      ],
      [
        "Planned/corrected vehicle",
        "Preserves assignment history."
      ],
      [
        "Observed transfer and proposal state",
        "Supports the handoff."
      ]
    ],
    "holdout": "Add a D2 V4 arrival observation but no approved substitution. Require the actual observation and unresolved assignment conflict both to remain visible.",
    "boundary": "Use original aliases and records. Exclude private stops and actual vehicle or staff data; official service decisions stay outside the test."
  }
}