{
  "title": "Organics processing batch lineage and disposition data for AI",
  "source_page": "https://fiund.com/industries/organics-treatment-batch-lineage-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A planned input diverted before mixing does not belong in the completed batch",
    "context": "An abstract batch diagram and original event cards use invented material labels and masses. No actual organics, contamination finding, recipe or processing procedure is supplied.",
    "records": [
      [
        "OB1",
        "Planned merge",
        "Inbound lots A=30 and B=20 practice units scheduled for batch X. Plan only."
      ],
      [
        "OB2",
        "Exception and actual merge",
        "B diverted to separate hold H before merge. Confirmed mock merge X contains A only, 30 units; event explicitly excludes B."
      ],
      [
        "OB3",
        "Outgoing record",
        "Output O links to X. Similar lot B1 appears in another plan with no completed event or X relationship."
      ]
    ],
    "question": "Which input lineage is supported for O, and can the original plan or B1's similar label establish B participation?",
    "answer": "OB2 explicitly defines the completed X merge as A only after B's diversion, and OB3 connects output O to X. O therefore has supported A lineage, while B remains associated with hold H rather than X. OB1's intended merge and OB3's B1 plan do not override the actual event. Preserve planned versus completed composition without inventing a release, treatment effectiveness or operational decision from the outgoing reference.",
    "failureModes": [
      "Assigning all planned inputs to an output despite a pre-merge diversion.",
      "Confusing a near-matching lot or outgoing reference with proof of completed processing."
    ],
    "fields": [
      [
        "Input lot and proposed parent batch",
        "Defines the plan."
      ],
      [
        "Diversion and confirmed merge membership",
        "Preserves actual lineage."
      ],
      [
        "Output parent and event state",
        "Supports the final association."
      ]
    ],
    "holdout": "Add a later approved merge of B into a distinct batch Y. Require O's X lineage to remain A-only.",
    "boundary": "Use fictional maps and original records. Exclude suppliers, agreements, contamination incidents and process recipes; operational and release decisions remain with staff."
  }
}