{
  "title": "Bed-and-breakfast guest preparation records for AI",
  "source_page": "https://fiund.com/industries/bed-breakfast-preparation-records-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Follow an amenity after a practice booking change",
    "context": "Two invented room aliases and dates describe an administrative handoff. No guest, actual reservation or private accommodation details appear.",
    "records": [
      [
        "REQUEST-B1",
        "Original preparation note",
        "A neutral practice welcome card is requested for room Birch on day 4."
      ],
      [
        "REVISION-B2",
        "Confirmed amendment",
        "The B1 request moves to room Cedar on day 5 and supersedes the earlier room and date."
      ],
      [
        "CHECK-B3",
        "Setup verification",
        "A verified card placement names Birch on day 4. No Cedar day-5 check is supplied."
      ]
    ],
    "question": "Does the supplied setup verification establish completion of the amended request?",
    "answer": "No. CHECK-B3 supports the original Birch day-4 setup. REVISION-B2 changes the target to Cedar on day 5, and the package has no matching verification for that amended target. State that the request changed and that the later setup remains unconfirmed. Do not move the earlier check to another room or date simply because it shares the request's history.",
    "failureModes": [
      "Reusing an old-room setup check as proof of the amended-room setup.",
      "Dropping the date when matching the verification to the request."
    ],
    "fields": [
      [
        "Request lineage",
        "Connect the amendment to B1 without erasing its prior target."
      ],
      [
        "Room alias and date",
        "Match both parts of the setup scope."
      ],
      [
        "Verification event",
        "Keep actual confirmation distinct from the requested arrangement."
      ]
    ],
    "holdout": "Add a Cedar day-5 check with the correct request reference. The model should now identify the amended setup as documented.",
    "boundary": "Use invented room aliases and a neutral prop only. Exclude real guests, room access, preferences, dietary information, bookings and payment data."
  }
}