{
  "title": "Security systems service tickets and verification records for AI",
  "source_page": "https://fiund.com/industries/security-system-service-closeout-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A generic clear-status display is distinct from an authorized verification event",
    "context": "An offline dashboard mockup uses fictional unit labels and original service cards. It contains no live alarm, configuration, credential, coverage map or device behavior.",
    "records": [
      [
        "SS1",
        "Ticket A",
        "Unit DEMO-A status display says CLEAR at time T. Display is generic and does not record who verified it."
      ],
      [
        "SS2",
        "Technician event",
        "Authorized mock role TECH signs verification V-A explicitly for ticket A/unit DEMO-A at T2. Original rubric requires this event for closeout evidence."
      ],
      [
        "SS3",
        "Ticket B",
        "Unit DEMO-B also displays CLEAR. Customer-style note reports issue stopped; no technician verification. Copy of V-A still names A."
      ]
    ],
    "question": "Which ticket has the stated verification evidence, and what can B's clear display or customer report establish?",
    "answer": "SS2 supplies the original rubric's authorized verification for A, separate from SS1's generic display. SS3 supports that B's simulated display reads CLEAR and a fictional speaker reports the issue stopped, but neither is a TECH verification for B. The copied V-A remains A-specific. Report B's missing closeout evidence without interpreting actual system performance, changing settings or inferring that any security protection is functioning.",
    "failureModes": [
      "Equating a status display or customer report with authorized verification.",
      "Using another ticket's technician sign-off because both dashboards show the same state."
    ],
    "fields": [
      [
        "Ticket and unit alias",
        "Defines the target."
      ],
      [
        "Display source versus reported observation",
        "Preserves attribution."
      ],
      [
        "Verification role, event and target",
        "Supports closeout evidence."
      ]
    ],
    "holdout": "Add a B technician event that is explicitly a diagnostic review rather than verification. Require the action type to remain distinct.",
    "boundary": "Use owned simulated screens and original forms. Exclude live systems, customer addresses, maps and credentials; authorized staff retain service decisions."
  }
}