{
  "title": "Biological product data for AI parent and aliquot records",
  "source_page": "https://fiund.com/industries/biologic-aliquot-parent-record-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A report attached to the wrong aliquot",
    "context": "Plain mock cards stand in for fictional samples. The exercise models administrative lineage only.",
    "records": [
      [
        "1",
        "Parent ledger",
        "Parent P4 split into A4 and B4; separate mock record packets."
      ],
      [
        "2",
        "Aliquot register",
        "A4 routed to packet Q11; B4 routed to Q12."
      ],
      [
        "3",
        "Report index",
        "Report Q11 names A4; Q12 attachment also names A4."
      ]
    ],
    "question": "What should be escalated in the record review?",
    "answer": "Q12 should be flagged because record 2 assigns it to B4 while the attachment in record 3 names A4. Q11's identifier agrees with its allocation. The shared parent P4 in record 1 does not make the aliquots interchangeable or resolve the conflicting attachment.",
    "failureModes": [
      "Resolving mismatches at parent-lot level",
      "Assuming the index is correct and overwriting an attachment silently"
    ],
    "fields": [
      [
        "aliquot_id",
        "Retains sample-level identity"
      ],
      [
        "packet_assignment",
        "States intended document route"
      ],
      [
        "attachment_identifier",
        "Preserves the conflicting observed field"
      ]
    ],
    "holdout": "Give a documented aliquot relabel event with prior and new IDs; require the approved map before accepting an alias.",
    "boundary": "No biological procedures, real samples, patient data, acceptance criteria or release authority."
  }
}