{
  "title": "Farmed shellfish tag and harvest-lot data for AI",
  "source_page": "https://fiund.com/industries/farmed-shellfish-harvest-tag-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A documented lot split preserves ancestry while a similar tag date does not",
    "context": "Original dummy tags use fictional area labels, dates and lots. They are not official tags, harvest permissions or a food-safety release record.",
    "records": [
      [
        "SHF1",
        "Origin tag",
        "Tag T1 links lot L1 to practice area A on day 2."
      ],
      [
        "SHF2",
        "Split record",
        "Authorized fictional split links L1 to child lots L1-A and L1-B on day 3. Child tags explicitly cite T1 and the split reference."
      ],
      [
        "SHF3",
        "Similar tag",
        "Tag T2 says area A, day 4, lot L2. No parent or split relationship to L1 supplied."
      ]
    ],
    "question": "Which child tags can be traced to the day-2 origin lot, and does T2's matching area establish the same ancestry?",
    "answer": "SHF1 and SHF2 explicitly connect L1-A and L1-B through the split record to T1's day-2 L1 origin. SHF3 describes another lot and day with no parent link, so its shared area label does not establish L1 ancestry. Preserve date, lot and split relationships together. The trace exercise establishes only the supplied documentary links, not current harvest authorization, product safety or permission to release a lot.",
    "failureModes": [
      "Joining lots by area name while ignoring harvest day and lot identity.",
      "Treating a reconstructed lineage as a public-health or release decision."
    ],
    "fields": [
      [
        "Tag, area alias and harvest date",
        "Defines the origin reference."
      ],
      [
        "Parent and child lot IDs",
        "Preserves the split."
      ],
      [
        "Verified link and missing relationship",
        "Separates supported ancestry from resemblance."
      ]
    ],
    "holdout": "Remove L1-B's parent reference while retaining its similar label. Require that child's trace to become unresolved rather than inferred from naming.",
    "boundary": "Use original dummy tags. Exclude leases, routes, security details and current permissions; real records require authorization from every controlling organization."
  }
}