{
  "title": "Recovery residence orientation and acknowledgment data for AI",
  "source_page": "https://fiund.com/industries/recovery-residence-orientation-ack-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Receipt of orientation version 1 does not acknowledge version 2",
    "context": "An invented program uses independently written orientation-cover cards. It includes no resident, site, attendance, treatment history or actual service record.",
    "records": [
      [
        "OA1",
        "Packet V1",
        "Original optional adult orientation session listed day 6. Mock receipt explicitly acknowledges program P/V1 on day 2."
      ],
      [
        "OA2",
        "Packet V2",
        "Approved revision changes that optional session to day 8. V2 dispatched day 4 with explicit P/V2 reference."
      ],
      [
        "OA3",
        "Reply state",
        "No V2 acknowledgment supplied. Generic inbox note says 'packet received' but gives no program, recipient or version."
      ]
    ],
    "question": "Which packet version has a matched acknowledgment, and what does V2's dispatch establish about its receipt?",
    "answer": "OA1 explicitly acknowledges P/V1. OA2 establishes approval and dispatch of P/V2, not its acknowledgment. OA3's generic note lacks the version and program references needed to close that gap. Preserve V1's receipt and V2's sent state separately rather than transfer an earlier acknowledgment to revised material. The optional-session change supplies no attendance or treatment information and the fixture concerns document workflow only.",
    "failureModes": [
      "Treating an earlier version's receipt as acknowledgment of a revised packet.",
      "Matching a generic inbox note without program or version identity."
    ],
    "fields": [
      [
        "Program and packet version",
        "Defines the document."
      ],
      [
        "Changed session and approval",
        "Limits the revision."
      ],
      [
        "Dispatch and exact acknowledgment target",
        "Separates delivery states."
      ]
    ],
    "holdout": "Add a V2 acknowledgment from another program P2. Require P's receipt gap to remain despite the matching version label.",
    "boundary": "Use original invented program records. Exclude residents, locations and histories; any later real-data use requires a separate privacy review."
  }
}