{
  "title": "Crane and hoist data for AI unit and test-report identity",
  "source_page": "https://fiund.com/industries/hoist-unit-test-report-identity-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A component record is not a completed-unit record",
    "context": "A paper equipment card references fictional assemblies. No real loads, certifications or test procedures appear.",
    "records": [
      [
        "1",
        "Unit register",
        "U4 contains module H2 and frame F1."
      ],
      [
        "2",
        "Report index",
        "R7 names module H2 only; R8 names completed unit U5."
      ],
      [
        "3",
        "Request",
        "Find completed-unit evidence for U4."
      ]
    ],
    "question": "Can either report support the requested scope?",
    "answer": "Neither. R7 concerns a component contained in U4, not U4 as assembled. R8 is at the right grain but names U5. Records 1–3 support retaining both references with their stated identities and flagging the missing completed-unit report for U4.",
    "failureModes": [
      "Using component test status as a whole-unit result",
      "Choosing a complete assembly report for the wrong serial"
    ],
    "fields": [
      [
        "unit_serial",
        "Identifies the completed assembly"
      ],
      [
        "subject_type",
        "Separates modules from units"
      ],
      [
        "report_scope",
        "Defines which identity a report covers"
      ]
    ],
    "holdout": "Include a multi-unit report with a serial appendix and check whether U4 actually appears.",
    "boundary": "No lifting limits, rigging advice, equipment operation or real qualification."
  }
}
