{
  "title": "Botanical manufacturing data for AI material identity records",
  "source_page": "https://fiund.com/industries/botanical-material-part-identity-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "One alias names two plant-part cards",
    "context": "All botanical aliases and object identifiers are invented. There is no extraction method or efficacy claim.",
    "records": [
      [
        "1",
        "Material glossary",
        "Alias Linden-X maps to root card R5 and leaf card L5."
      ],
      [
        "2",
        "Receipt ticket",
        "Bag B2 is marked Linden-X L5."
      ],
      [
        "3",
        "Output ledger",
        "Batch E9 references B2; summary field says root."
      ]
    ],
    "question": "Which field needs reconciliation?",
    "answer": "The root description on record 3 conflicts with the L5 leaf identity in records 1 and 2. E9 links to B2 through its input reference. Keep the canonical material code and the conflicting free-text description visible; the shared alias alone cannot identify plant part.",
    "failureModes": [
      "Mapping a shared alias directly to a single plant part",
      "Assuming a ledger summary independently verified the physical material"
    ],
    "fields": [
      [
        "part_code",
        "Disambiguates common aliases"
      ],
      [
        "input_bag_id",
        "Joins receipt to downstream record"
      ],
      [
        "identity_conflict",
        "Retains conflicting ledger text"
      ]
    ],
    "holdout": "Use a receipt with only the alias and no part code; require an unresolved part label.",
    "boundary": "No actual botanical species, extraction parameters, sourcing records or therapeutic claims."
  }
}