{
  "title": "Employment agency job-order and referral records for AI",
  "source_page": "https://fiund.com/industries/employment-placement-referral-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The job-order version at submission can differ from the later circulation version",
    "context": "An original requisition and fabricated scheduling response illustrate document verification. No candidate, résumé, demographic, assessment or placement decision is represented.",
    "records": [
      [
        "EP1",
        "Requisition J v1",
        "Approved from day 1: Saturday shifts required under this fictional job-order wording."
      ],
      [
        "EP2",
        "Signed v2 revision",
        "Issued day 5, effective day 10: Saturdays become optional. Other mock terms unchanged."
      ],
      [
        "EP3",
        "Referral packet",
        "Submitted day 8 with invented response 'weekday availability only.' Recirculated day 12; no revised review note supplied."
      ]
    ],
    "question": "Which schedule language applied to the day-8 submission, and what should a day-12 document review flag without deciding placement?",
    "answer": "EP1's required-Saturday wording applies on day eight because EP2's signed change does not take effect until day ten. By EP3's day-12 recirculation, v2 says Saturdays are optional, but the packet lacks an updated review note. Cite both effective versions and flag the stale review basis rather than make an applicant decision or infer anything about capability, reliability or employment eligibility from the fictional response.",
    "failureModes": [
      "Applying a signed future-effective revision before its start date.",
      "Reusing a prior document review after circulation under changed terms without identifying the version difference."
    ],
    "fields": [
      [
        "Requisition and approved version",
        "Defines the brief."
      ],
      [
        "Issue versus effective date",
        "Supports as-of selection."
      ],
      [
        "Submission, recirculation and review source",
        "Exposes stale document checks."
      ]
    ],
    "holdout": "Change the revision to a role-location update rather than schedule. Require the reviewer to identify the new field without assuming every change concerns availability.",
    "boundary": "Use original fictitious requisitions and subjects. Exclude candidate records and client forms; staff retain all placement and employment decisions."
  }
}