{
  "title": "Fertilizer blending data for AI plan and execution records",
  "source_page": "https://fiund.com/industries/fertilizer-blend-plan-execution-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The plan names a component the ledger never confirms",
    "context": "Paper tokens represent three mock inputs; quantities, chemical identities and settings are omitted.",
    "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": "Which execution claim can be made about C?",
    "answer": "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.",
    "failureModes": [
      "Counting staged stock as consumed",
      "Declaring a component absent solely from missing documentation"
    ],
    "fields": [
      [
        "plan_component",
        "Tracks the intended input"
      ],
      [
        "event_component",
        "Records observed execution separately"
      ],
      [
        "evidence_state",
        "Keeps missing, confirmed and contradictory entries distinct"
      ]
    ],
    "holdout": "Use a verified substitution event and require retaining both the original plan and replacement identity.",
    "boundary": "No blend proportions, application rates, chemical process advice or real formulations."
  }
}