{
  "title": "Fitness center equipment status records for AI",
  "source_page": "https://fiund.com/industries/fitness-center-equipment-status-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A maintenance request is not a recorded return-to-availability decision",
    "context": "Two imaginary equipment assets are represented by paper cards. The task reads administrative evidence without giving exercise guidance or certifying equipment safety.",
    "records": [
      [
        "FC1",
        "Asset A work order",
        "Request logged day 1. Qualified role Q records completed review and authorized practice status available on day 3."
      ],
      [
        "FC2",
        "Asset B work order",
        "Request logged day 2. Technician message says visit planned day 4; no completion or status authorization."
      ],
      [
        "FC3",
        "Generic dashboard note",
        "Equipment reviewed this week, without asset IDs. No source ties that note to B."
      ]
    ],
    "question": "Which administrative status change is explicitly supported, and can the visit plan or generic note establish B as available?",
    "answer": "FC1 explicitly records role Q's authorized status change for A on day 3. FC2 provides only a request and planned visit for B, while FC3 lacks an asset-specific relationship. Neither closes B's review or supplies its availability decision. Report the last supported B state and needed qualified review rather than using a broad dashboard note or calendar plan as equipment certification.",
    "failureModes": [
      "Marking a requested or scheduled maintenance item complete automatically.",
      "Applying an asset-unspecified dashboard statement to every open work order."
    ],
    "fields": [
      [
        "Asset and work-order identity",
        "Makes each review specific."
      ],
      [
        "Request, planned visit and completed review",
        "Preserves distinct event states."
      ],
      [
        "Authorized status source",
        "Shows who recorded the availability decision."
      ]
    ],
    "holdout": "Record B's visit completed but follow-up review still pending. Require a completed-visit state without an inferred availability approval.",
    "boundary": "Use fabricated records or approved static props. Exclude member activity, health data, trainer schedules, incidents, security details and operating procedures."
  }
}