{
  "title": "Heavy civil earthwork lift records for AI review",
  "source_page": "https://fiund.com/industries/civil-earthwork-lift-review-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A recheck closes only the layer and observation it names",
    "context": "An abstract cross-section contains training layers L1 and L2. Invented test codes and dispositions measure association and event sequence without evaluating real earthwork.",
    "records": [
      [
        "EL1",
        "Initial practice test",
        "Layer L1, point Q: status needs review under test T1."
      ],
      [
        "EL2",
        "Rework and recheck record",
        "Layer L1, point Q: rework logged, then reviewed recheck T2 records exercise status complete."
      ],
      [
        "EL3",
        "Separate test",
        "Layer L2, point Q: test T2-B remains needs review. A summary shortens both point labels to Q."
      ]
    ],
    "question": "Which exact observation has a documented completed recheck, and does the shared point label close the L2 review?",
    "answer": "EL1 and EL2 establish a sequence for L1 at point Q: initial review flag, logged rework and completed reviewed recheck T2. EL3 is L2 at point Q with its own open status. The shortened Q label does not erase the layer distinction. Report the completed L1 sequence and preserve L2's open review rather than applying one layer's outcome to both.",
    "failureModes": [
      "Joining tests on point Q alone while dropping the layer key.",
      "Treating a rework log as the completed recheck before the reviewed observation occurs."
    ],
    "fields": [
      [
        "Layer-plus-point identity",
        "Disambiguates repeated location labels."
      ],
      [
        "Initial, rework and recheck events",
        "Preserves the chronology supporting a status."
      ],
      [
        "Review outcome source",
        "Keeps an administrative summary from replacing the underlying test."
      ]
    ],
    "holdout": "Make the recheck timestamp precede the recorded rework event. Require an explicit chronology flag rather than a silently reordered completion narrative.",
    "boundary": "Use synthetic cross-sections and status labels. Exclude real infrastructure geometry, material properties, coordinates, equipment settings and engineering documents. No structural-safety conclusion is requested."
  }
}