{
  "title": "Shipyard data for AI work-item closeout chains",
  "source_page": "https://fiund.com/industries/shipyard-work-item-closeout-chain-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Closed status needs evidence for the named work item",
    "context": "A fictional shipyard document board uses neutral office tasks. No vessel system, plans or repair instructions appear.",
    "records": [
      [
        "1",
        "Work register",
        "Vessel exercise V2 has item W1 and W2."
      ],
      [
        "2",
        "Index",
        "Completion note C8 names W1; both items share folder V2."
      ],
      [
        "3",
        "Dashboard",
        "W2 marked closed with C8 reference."
      ]
    ],
    "question": "Is W2 closeout supported?",
    "answer": "No. C8 applies to W1 under record 2 and the shared V2 folder from record 1 does not extend its scope. Flag record 3's unsupported closeout. W1 can retain its own linked note without changing W2's review or completion state.",
    "failureModes": [
      "Using a vessel-level folder as work-item proof",
      "Closing a neighboring item using the wrong note"
    ],
    "fields": [
      [
        "work_item_id",
        "Defines evidence grain"
      ],
      [
        "completion_note_subject",
        "Checks exact applicability"
      ],
      [
        "closeout_status",
        "Stays separate until supported"
      ]
    ],
    "holdout": "Use a note explicitly covering both work items and require two scoped links to the same document.",
    "boundary": "No actual vessel identity, ship systems, repair steps, shipyard plans or seaworthiness."
  }
}