{
  "title": "Boiler and heat-exchanger data for AI report identity",
  "source_page": "https://fiund.com/industries/boiler-exchanger-data-report-identity-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A system-level folder contains a component-level report",
    "context": "A mock diagram shows two paper boxes. It carries no pressure, temperature, design or certification information.",
    "records": [
      [
        "1",
        "Unit map",
        "System U7 includes component E2 and component E3."
      ],
      [
        "2",
        "Report index",
        "Report R5 names E3; stored under U7."
      ],
      [
        "3",
        "Request",
        "Find the evidence for E2 specifically."
      ]
    ],
    "question": "Can R5 be attached to E2?",
    "answer": "No. The common U7 folder is consistent with record 1 but R5 expressly identifies E3 in record 2. It can be listed under U7 with E3 scope; record 3's E2 query remains unmet unless a distinct or explicitly shared report appears.",
    "failureModes": [
      "Inferring report coverage from a folder name",
      "Assigning an E3 report to a sibling component"
    ],
    "fields": [
      [
        "parent_unit",
        "Groups components without expanding evidence"
      ],
      [
        "component_report_key",
        "Identifies the component named by the report"
      ],
      [
        "request_scope",
        "Specifies whether an exact component match is needed"
      ]
    ],
    "holdout": "Add a multi-component report naming both E2 and E3 and preserve page-level scope for each.",
    "boundary": "Paper records only; exclude genuine equipment reports, operating guidance and compliance statements."
  }
}
