INDUSTRY FIELD GUIDE
Botanical manufacturing data for AI material identity records
FDA publishes botanical-drug development guidance.
NAICS 325411 · Medicinal and Botanical Manufacturing
FDA publishes botanical-drug development guidance. A manufacturer can use that context to propose a document task that preserves the material identity and source references actually recorded, with no claim about therapeutic use. FDA botanical-drug guidance
Create fictional botanical aliases, a material ticket and an extraction-lot ledger with invented identifiers. State plant-part and preparation descriptors explicitly in the exercise glossary. Ask which certificate belongs to the selected material. Include a supplier description that identifies only a broader family and a corrected lot reference whose original remains visible. The key should use the specific supplied identity fields and effective correction.
Annotate material identity, stated part, preparation reference, input lot, output lot and document version. Hold out a new alias set for evaluation. Score family-level descriptions treated as complete identity, wrong-lot matches and use of the superseded record independently. A sample image should not establish composition or efficacy when the evidence supplies neither.
Use invented records without material preparation. Actual sourcing histories, proprietary methods and outside laboratory documents require source-specific authority and qualified review. A licensing brief should name the identity-association task and checked examples. Confirm buyer scope before preparing a commercial archive.
Discuss this original manufacturing sample with Fiund
Original Fiund exercise
One alias names two plant-part cards
All botanical aliases and object identifiers are invented. There is no extraction method or efficacy claim.
| Record | Source | What it 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 for the model
Which field needs reconciliation?
Show the reference answer and checks
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.
- Mapping a shared alias directly to a single plant part
- Assuming a ledger summary independently verified the physical material
Fields to preserve
- part_code
- Disambiguates common aliases
- input_bag_id
- Joins receipt to downstream record
- identity_conflict
- Retains conflicting ledger text
Test another case
Use a receipt with only the alias and no part code; require an unresolved part label.
No actual botanical species, extraction parameters, sourcing records or therapeutic claims.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.