{
  "title": "Continuing care retirement community transition data for AI",
  "source_page": "https://fiund.com/industries/retirement-community-service-transition-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A tentative reservation date is different from an effective service transfer",
    "context": "Two abstract service levels and generic location aliases form an invented administrative timeline. No resident, care need, contract, payment or access detail is represented.",
    "records": [
      [
        "RT1",
        "Proposal and reservation",
        "Fictional record R proposes level L2; tentative reservation at location B starts day 10. Proposal unsigned."
      ],
      [
        "RT2",
        "Signed mock transfer",
        "R transfer from L1/location A to L2/location B effective day 14. Explicitly supersedes proposed start date."
      ],
      [
        "RT3",
        "Service event log",
        "No separate L2 service-start event or completion record supplied. Requested as-of date day 12."
      ]
    ],
    "question": "What transition date is authorized by the supplied document, and does the day-12 packet establish that L2 service has started?",
    "answer": "RT2 documents an effective transfer date of day 14, replacing RT1's tentative day-10 reservation date. For day 12, that transfer is still future-dated, and RT3 supplies no separate L2 start event. Preserve the signed future transition and lack of current start evidence rather than treat a reserved location or proposal as completed service. The fixture does not evaluate care needs, eligibility or an actual resident's placement.",
    "failureModes": [
      "Using a tentative reservation as the actual service-transfer date.",
      "Inferring service commencement from a future signed transfer without a matching event."
    ],
    "fields": [
      [
        "Record alias and abstract levels",
        "Defines the transition."
      ],
      [
        "Reservation versus effective date",
        "Separates planned stages."
      ],
      [
        "Authorization and start-event evidence",
        "Supports the limited status summary."
      ]
    ],
    "holdout": "Move the review date to day 15 but retain no start event. Require the transfer's effective date to be recognized while actual service occurrence remains unverified.",
    "boundary": "Use original forms and generic places. Exclude residents, care records, contracts and facility access; qualified staff retain care and eligibility decisions."
  }
}