{
  "title": "Temporary shelter capacity and reporting window data for AI",
  "source_page": "https://fiund.com/industries/temporary-shelter-capacity-window-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A later capacity update cannot be inserted into an earlier snapshot",
    "context": "An invented dashboard uses abstract spaces and a fictional site. It contains no live capacity, location, participant, referral or placement information.",
    "records": [
      [
        "SCW1",
        "10:00 snapshot",
        "Site DEMO has 8 total practice spaces. Two explicitly held, leaving 6 not held at that timestamp under this fixture's rule."
      ],
      [
        "SCW2",
        "Later update",
        "Received 10:20, effective 10:15: one additional space placed on hold, total held becomes 3. No retroactive correction to 10:00."
      ],
      [
        "SCW3",
        "Request",
        "Question A asks what the 10:00 snapshot reported. Question B asks for current availability at 11:00; no events after 10:20 supplied."
      ]
    ],
    "question": "Which counts are supported for the historical snapshot and latest supplied update, and does either guarantee an 11:00 space?",
    "answer": "SCW1 supports six not-held practice spaces at 10:00. SCW2 supports five after its 10:15 effective change, known from 10:20 onward; it does not revise the earlier snapshot. SCW3 supplies no later refresh or direct availability confirmation, so neither count guarantees an 11:00 place. Preserve snapshot time, update-effective time and receipt time separately without inferring any person's placement or actual service access.",
    "failureModes": [
      "Applying a later nonretroactive hold to an earlier snapshot.",
      "Treating a last-known aggregate as a guaranteed current space or a placement decision."
    ],
    "fields": [
      [
        "Site and capacity unit",
        "Defines the aggregate."
      ],
      [
        "Snapshot, effective and received times",
        "Preserves temporal scope."
      ],
      [
        "Held count and refresh state",
        "Limits the availability claim."
      ]
    ],
    "holdout": "Make the update explicitly correct an erroneous 10:00 hold count. Require a revised historical snapshot while preserving what was originally reported.",
    "boundary": "Use wholly invented counts and sites. Exclude real routes and exports; providers retain referral and placement decisions."
  }
}