{
  "title": "Battery manufacturing data for AI cell and pack evidence",
  "source_page": "https://fiund.com/industries/battery-cell-pack-test-scope-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A cell report does not become a pack result",
    "context": "Fictional identifiers describe paper cell, module and pack tokens. There is no electrical configuration or test procedure.",
    "records": [
      [
        "1",
        "Build ledger",
        "Pack P7 contains module M3, which contains cell C4."
      ],
      [
        "2",
        "Report index",
        "R1 covers C4; R2 covers M3; no P7 entry."
      ],
      [
        "3",
        "Request",
        "Retrieve evidence on the completed P7 pack."
      ]
    ],
    "question": "Which reports meet the requested assembly scope?",
    "answer": "Neither. Records 1 and 2 show that R1 and R2 concern descendants of P7 at different levels. Their links can be retained in a parts evidence view, but they do not constitute a completed-pack report for the exact request in record 3.",
    "failureModes": [
      "Treating lower-level evidence as pack validation",
      "Joining only through containment without preserving report grain"
    ],
    "fields": [
      [
        "assembly_level",
        "Distinguishes cell, module and pack"
      ],
      [
        "tested_identifier",
        "Identifies the actual subject"
      ],
      [
        "parent_pack_link",
        "Supports navigation without expanding scope"
      ]
    ],
    "holdout": "Provide a pack report for P7 before a module replacement and require the configuration date for applicability.",
    "boundary": "No real cells, charging or assembly advice, safety claims, electrical values or certification."
  }
}
