{
  "title": "Packaging machinery state logs for AI fault review",
  "source_page": "https://fiund.com/industries/packaging-machine-state-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An upstream hold can coexist with a downstream fault label",
    "context": "Fictional event records use plain state names. No machine control instructions appear.",
    "records": [
      [
        "1",
        "Upstream log",
        "Commanded hold active 10:00–10:04."
      ],
      [
        "2",
        "Downstream log",
        "Fault-labeled interval 10:01–10:03; fault reason blank."
      ],
      [
        "3",
        "Summary rule",
        "Keep each subsystem's state; derive causation only from explicit evidence."
      ]
    ],
    "question": "What should the joined timeline show?",
    "answer": "The downstream label overlaps the upstream hold for two minutes and is fully nested within it. Keep both states and their source systems under records 1–3. Overlap alone does not prove the upstream command caused the fault label or that either label should overwrite the other.",
    "failureModes": [
      "Replacing one subsystem's label with the other's",
      "Inferring fault cause solely from time overlap"
    ],
    "fields": [
      [
        "subsystem_id",
        "Preserves state source"
      ],
      [
        "state_interval",
        "Supports exact overlap calculation"
      ],
      [
        "cause_evidence",
        "Distinguishes coincidence from documented causal link"
      ]
    ],
    "holdout": "Give one fault crossing the hold end and report both overlapping and nonoverlapping portions.",
    "boundary": "No actual packaging-machine operation, line settings, telemetry credentials or troubleshooting instructions."
  }
}