{
  "title": "Facilities service handoff records for AI workflow evaluation",
  "source_page": "https://fiund.com/industries/facilities-service-handoff-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A service matrix selects the next authority, while dispatch does not prove owner approval",
    "context": "An original fictional issue concerns a loose inert sign on a mock room prop. It includes no credentials, tenant, actual plan, building control or repair procedure.",
    "records": [
      [
        "FH1",
        "Contract C1 matrix",
        "Housekeeping reports the issue; dispatcher may assign review. Replacement action needs site-owner approval. Matrix explicitly applies to mock site A."
      ],
      [
        "FH2",
        "Site A timeline",
        "Housekeeping report R, dispatcher assignment D and owner approval O explicitly link the same issue I. No actual replacement event supplied."
      ],
      [
        "FH3",
        "Site B packet",
        "Similar sign issue under contract C2 requires contractor-manager approval. Only a dispatcher assignment exists; no manager approval. C1 owner signature copied as an attachment."
      ]
    ],
    "question": "Which authority handoff is supported at A, and why does the same symptom or copied approval not resolve B?",
    "answer": "FH1 and FH2 support A's report, dispatch and required owner approval for issue I, while replacement completion remains undocumented. FH3 uses a different contract requiring contractor-manager approval; its dispatch and copied C1 owner signature do not satisfy that stated matrix. Route B's missing approval to the named role rather than generalize from the symptom or another site's authority. This fixture evaluates routing, not facility-control or repair decisions.",
    "failureModes": [
      "Applying one site's responsibility matrix to a similar issue under another contract.",
      "Treating assignment or another site's approval as permission for the next action."
    ],
    "fields": [
      [
        "Site, contract and issue",
        "Selects the responsibility matrix."
      ],
      [
        "Current role and required approval",
        "Defines the handoff."
      ],
      [
        "Linked authority source and completion state",
        "Separates permission from execution."
      ]
    ],
    "holdout": "Add B's manager acknowledgment saying review pending. Require the correct role match without calling it approval.",
    "boundary": "Use fabricated matrices and inert props. Exclude access details, real incidents and operating systems; facility and contractor rights need separate review."
  }
}