{
  "title": "Bus and mixed-mode transit update data for AI evaluation",
  "source_page": "https://fiund.com/industries/transit-bus-trip-update-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A stop cancellation applies to one dated trip rather than every departure on the route",
    "context": "A synthetic bus-and-rail timetable uses invented stops and service dates. There is no rider, vehicle assignment, live dispatch or actual travel recommendation.",
    "records": [
      [
        "BTU1",
        "Base schedule",
        "Route R, day D1: trip A serves stops S1–S3, arrival S3 10:00. Trip B serves same stops, arrival S3 10:30."
      ],
      [
        "BTU2",
        "Trip updates",
        "A's S3 stop canceled on D1; other A stops retained. B delayed 10 minutes with S3 retained, revised arrival 10:40."
      ],
      [
        "BTU3",
        "Rail connection",
        "Rail departure S3 10:35 listed for D0 only. No current D1 rail update, transfer rule or booking evidence."
      ]
    ],
    "question": "What changed for each D1 bus trip, and does the supplied rail record establish an onward connection?",
    "answer": "BTU2 removes S3 only from A on D1, while B still serves S3 with revised arrival 10:40. Do not apply A's stop cancellation to B or treat B's delay as a route-wide cancellation. BTU3 belongs to D0 and lacks current D1 transfer evidence, so it cannot establish an onward rail connection. Preserve trip, service date and affected stop rather than infer a journey from a route name alone.",
    "failureModes": [
      "Propagating a trip-specific stop cancellation across the route.",
      "Using another service day's departure or stale connection information as current evidence."
    ],
    "fields": [
      [
        "Route, trip and service day",
        "Defines the update scope."
      ],
      [
        "Stop and cancellation/delay type",
        "Preserves the actual change."
      ],
      [
        "Connection date and transfer evidence",
        "Limits onward-journey claims."
      ]
    ],
    "holdout": "Supply a D1 rail departure at 10:45 but no minimum-transfer rule. Require timetable proximity to be distinguished from a confirmed usable connection.",
    "boundary": "Use invented schedules or separately cleared public feeds. Exclude riders, staff and identifiable vehicle assignments."
  }
}