{
  "title": "Liquid pipeline batch records for offline AI evaluation",
  "source_page": "https://fiund.com/industries/liquid-pipeline-batch-records-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A canceled nomination does not establish an observed batch movement",
    "context": "An entirely fictional retrospective packet uses abstract batch and commodity labels. It contains no route, composition, pressure, flow, control interface or operating procedure.",
    "records": [
      [
        "PB1",
        "Batch A receipt",
        "Verified original receipt R-A explicitly names batch DEMO-A and abstract commodity C1 at reference time T1."
      ],
      [
        "PB2",
        "Batch B nomination",
        "Nomination N-B schedules DEMO-B, commodity C2, near T1. Later cancellation explicitly names N-B; no movement confirmation supplied."
      ],
      [
        "PB3",
        "Summary metadata",
        "R-A is an observed receipt; N-B is a schedule and its cancellation is administrative. No C1-to-C2 equivalence or B receipt exists."
      ]
    ],
    "question": "Which batch supports the observed receipt, and does B's similar schedule establish movement or a commodity substitution?",
    "answer": "PB1 explicitly supports receipt of DEMO-A under commodity label C1. PB2 schedules then cancels DEMO-B and supplies no movement evidence. PB3 distinguishes those record types and provides no equivalence between commodities. Similar timing cannot attach R-A to B or establish a substitution. Report A's receipt and B's canceled schedule with their separate sources, leaving unobserved movement unresolved without making any pipeline operational decision.",
    "failureModes": [
      "Treating a nomination as proof that a batch moved.",
      "Matching by nearby times while ignoring batch identity, commodity label and cancellation."
    ],
    "fields": [
      [
        "Batch and abstract commodity",
        "Defines the record scope."
      ],
      [
        "Scheduled versus observed event type",
        "Separates intention from evidence."
      ],
      [
        "Receipt reference and cancellation target",
        "Supports the retrospective summary."
      ]
    ],
    "holdout": "Add a B receipt at a different time but omit its commodity label. Require movement evidence to resolve while commodity attribution remains incomplete.",
    "boundary": "Use specialist-reviewed dummy records only. Exclude operational values and live systems; no navigation, transfer or control action is taken."
  }
}