INDUSTRY FIELD GUIDE
Fertilizer blending data for AI plan and execution records
Fertilizer mixing records can contain both an intended blend and the additions actually recorded.
NAICS 325314 · Fertilizer (Mixing Only) Manufacturing
Fertilizer mixing records can contain both an intended blend and the additions actually recorded. Minnesota's agriculture department supplies public label context. An original exercise can test whether the assistant follows execution evidence before choosing a product reference. Minnesota fertilizer product-label context
Create a fictional blend plan, component tickets and addition ledger. Change one component identifier during execution while retaining the original plan. Ask which inputs are documented for the finished batch and which product card is supported. Include a replacement purchase order that was never received and a staged component with no addition entry. The key should preserve those differences instead of treating every listed input as used.
Annotate component, planned quantity, actual entry, batch and document status. Evaluation can use a different number of components and a corrected addition record. Score use of the plan as execution, invented additions and wrong-version selection independently. The exercise should supply no production recipe or application advice beyond its fictional record relationships.
Use invented values and self-authored documents. Real customer blends, supplier certificates and proprietary operating data require permission and specialist review. Describe the execution-review task and checked examples to prospective buyers. Their accepted brief should determine the source relationships and historical depth worth preparing for licensing.
Discuss this original manufacturing sample with Fiund
Original Fiund exercise
The plan names a component the ledger never confirms
Paper tokens represent three mock inputs; quantities, chemical identities and settings are omitted.
| Record | Source | What it records |
|---|---|---|
| 1 | Plan | Job J31 expects component tokens A, B and C. |
| 2 | Event ledger | Recorded joins are A and B; no C event is present. |
| 3 | Shift note | A C token was staged nearby, but the note does not say it was added. |
Question for the model
Which execution claim can be made about C?
Show the reference answer and checks
C was planned in record 1 and staged according to record 3, but its addition is not documented in record 2. Mark execution evidence missing for C. A staged token does not establish use, and absent logging alone does not prove that it was omitted.
- Counting staged stock as consumed
- Declaring a component absent solely from missing documentation
Fields to preserve
- plan_component
- Tracks the intended input
- event_component
- Records observed execution separately
- evidence_state
- Keeps missing, confirmed and contradictory entries distinct
Test another case
Use a verified substitution event and require retaining both the original plan and replacement identity.
No blend proportions, application rates, chemical process advice or real formulations.
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.