{
  "title": "Brake component data for AI batch and report scope",
  "source_page": "https://fiund.com/industries/brake-component-batch-report-scope-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A same-family report can name a different batch",
    "context": "Fictional component and specimen cards contain document identifiers only, without testing or safety guidance.",
    "records": [
      [
        "1",
        "Batch map",
        "Component lot B7 sampled as S1; B8 sampled as S2."
      ],
      [
        "2",
        "Report index",
        "Report R1 names S2 and the shared component family."
      ],
      [
        "3",
        "Query",
        "Retrieve the specimen report for B7."
      ]
    ],
    "question": "Is R1 valid evidence for the requested batch?",
    "answer": "No. S2 belongs to B8 under record 1, so R1 in record 2 does not match B7's specimen. Preserve the common family for navigation, but keep exact batch evidence missing. The lookup does not authorize any component use or safety conclusion.",
    "failureModes": [
      "Using component family instead of specimen lineage",
      "Treating report presence as evidence for all lots"
    ],
    "fields": [
      [
        "lot_id",
        "Pins requested material"
      ],
      [
        "specimen_id",
        "Connects lot and report"
      ],
      [
        "document_scope",
        "Preserves exact subject"
      ]
    ],
    "holdout": "Include a report expressly scoped to a combined batch with a documented sampling map; keep the sampled object and stated scope distinct.",
    "boundary": "No brake design, testing thresholds, fit, service or vehicle safety decisions."
  }
}