{
  "title": "Industrial machinery data for AI change-order execution",
  "source_page": "https://fiund.com/industries/industrial-machine-change-order-execution-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An approved change is not an executed change",
    "context": "A toy machine module and fictional ticket log cover a single documented change.",
    "records": [
      [
        "1",
        "Change request",
        "CR7 approves replacing module A with B after build 20."
      ],
      [
        "2",
        "Build traveler",
        "Build 24 still lists A; no execution event for CR7."
      ],
      [
        "3",
        "Photo",
        "Module tag A visible on 24."
      ]
    ],
    "question": "What should the build status say about CR7?",
    "answer": "CR7 is applicable to build 24 under record 1, but its execution is not supported. Records 2 and 3 instead show A, the pre-change module. Flag an approved-versus-built discrepancy; do not count approval as installation or infer why it was not executed.",
    "failureModes": [
      "Treating approval as installation evidence",
      "Ignoring the effective build range"
    ],
    "fields": [
      [
        "change_request_id",
        "Links the approved action"
      ],
      [
        "build_effectivity",
        "Defines where it should apply"
      ],
      [
        "executed_component",
        "Records what was actually installed"
      ]
    ],
    "holdout": "Log an approved deferral for builds 21–25 only; keep build 24 distinct from build 26.",
    "boundary": "No real industrial equipment drawings, production changes, maintenance procedures or safety conclusions."
  }
}