{
  "title": "School and employee bus stop-change records for AI",
  "source_page": "https://fiund.com/industries/school-employee-bus-stop-change-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A newer draft file does not replace the approved stop for another service date",
    "context": "An original schedule fixture uses a generic training run and abstract stops. It contains no child, employee, school, home, rider list or live vehicle location.",
    "records": [
      [
        "SBX1",
        "Approved run record",
        "Run R/day D1 serves stop S1. Original approval explicitly names R and D1."
      ],
      [
        "SBX2",
        "Authorized revision",
        "For R/D2 only, signed notice changes S1 to S2. No retroactive D1 change."
      ],
      [
        "SBX3",
        "Later file",
        "Draft saved after the revision proposes S3 for R/D3, unsigned. Separate approved S3 note names run R2, not R."
      ]
    ],
    "question": "Which stops are supported for R on D1 and D2, and can the later draft or R2 note authorize S3 for R?",
    "answer": "SBX1 supports S1 for R/D1. SBX2 supports S2 for R/D2 only, preserving D1's earlier stop. SBX3's R/D3 proposal remains unsigned, while its signed S3 note belongs to another run. Neither establishes an approved S3 change for R. Keep service date and run identity with approval status rather than select the newest file or an approved record with the wrong target. The task gives no live boarding instruction.",
    "failureModes": [
      "Applying a future-date stop change to an earlier run.",
      "Treating a newer draft or another route's approval as current authority."
    ],
    "fields": [
      [
        "Run and service date",
        "Defines applicability."
      ],
      [
        "Approved stop and changed field",
        "Preserves the revision."
      ],
      [
        "Signature and draft state",
        "Limits authorization."
      ]
    ],
    "holdout": "Ask for R/D3 with no new approval. Require an unresolved future-change status rather than inherit R2's stop.",
    "boundary": "Use fabricated schedules and notices. Exclude actual locations and access plans; stop selection and notifications remain under authorized human control."
  }
}