{
  "title": "Cement manufacturing data for AI silo and report-period matching",
  "source_page": "https://fiund.com/industries/cement-silo-report-period-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A silo report does not cover a later load automatically",
    "context": "A fictional silo inventory uses plain lot keys and report references. No material recipe or engineering threshold is supplied.",
    "records": [
      [
        "1",
        "Ledger",
        "Silo S1 uses lot L4 until 09:00; L5 begins at 09:00 in this simplified map."
      ],
      [
        "2",
        "Dispatch ticket",
        "Load D3 associated with S1 at 09:20."
      ],
      [
        "3",
        "Report index",
        "R4 applies to S1/L4; no L5 report in packet."
      ]
    ],
    "question": "Is R4 applicable to D3 under the given map?",
    "answer": "No. D3 falls in the L5 interval under records 1 and 2, while R4 explicitly covers L4 in record 3. Silo identity alone is not enough to attach the report. Record L5 and flag missing lot-specific evidence.",
    "failureModes": [
      "Treating silo ID as an unchanging material key",
      "Applying the last available report to the next lot"
    ],
    "fields": [
      [
        "silo_id",
        "Groups dispatch activity"
      ],
      [
        "lot_effectivity",
        "Resolves the intended inventory interval"
      ],
      [
        "report_lot_scope",
        "Limits report transfer"
      ]
    ],
    "holdout": "Use a logged overlap with no allocation map and require abstention from an exact lot assignment.",
    "boundary": "No actual silo operations, material standards, dispatch records or conformity claims."
  }
}