{
  "title": "Industrial machinery repair verification and service release data for AI",
  "source_page": "https://fiund.com/industries/industrial-repair-return-to-service-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A completed repair ticket and an owner's release belong to separate authority chains",
    "context": "A decommissioned training-unit record pack uses invented assets and repair labels. It contains no energized equipment, control screen, isolation steps or maintenance instructions.",
    "records": [
      [
        "IR1",
        "Practice asset A service ticket",
        "Part replacement recorded; technician marks repair complete."
      ],
      [
        "IR2",
        "Inspection record",
        "Reviewer confirms the stated A inspection scope. Owner's A return-to-service approval absent."
      ],
      [
        "IR3",
        "Attached release",
        "Signed release names neighboring asset B only, despite being filed in A's folder."
      ]
    ],
    "question": "Which repair and inspection stages are supported for A, and can B's release or the completed ticket establish A's owner approval?",
    "answer": "IR1 supports the technician's completed repair entry, and IR2 supplies a separate inspection record for A. Neither is the missing owner release. IR3 explicitly names B and cannot authorize A through folder placement. Report A's documented stages and pending owner authority independently rather than treating repair completion, inspection and return-to-service as one interchangeable status.",
    "failureModes": [
      "Using a neighboring asset's release to close A's authorization.",
      "Treating a technician-completed ticket as the equipment owner's separate return-to-service approval."
    ],
    "fields": [
      [
        "Asset identity and document scope",
        "Prevents cross-asset release matching."
      ],
      [
        "Technician, reviewer and owner roles",
        "Preserves who recorded each stage."
      ],
      [
        "Repair versus release state",
        "Makes the unresolved authority visible."
      ]
    ],
    "holdout": "Supply an owner approval for A limited to further bench review. Require the model to preserve that narrow scope rather than interpret it as operating release.",
    "boundary": "Use dummy records and decommissioned props only. Exclude live controls, energy-isolation details, clients and actual repair manuals."
  }
}