{
  "title": "Port container availability records for AI review",
  "source_page": "https://fiund.com/industries/port-container-availability-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Physical presence, document release and an appointment slot are independent readiness conditions",
    "context": "Two fictitious containers follow an original three-condition rubric. It is an inert records exercise with no real customs data, port position, access detail or pickup instruction.",
    "records": [
      [
        "PCA1",
        "Practice readiness rule",
        "A review packet is complete only when discharge, valid document release and a matching appointment are all confirmed for the same container and date."
      ],
      [
        "PCA2",
        "Container A",
        "Discharge confirmed. Document release pending. Later appointment confirmed for A/day 2; no release completion."
      ],
      [
        "PCA3",
        "Container B",
        "Discharge and valid day-2 release confirmed. No appointment slot record; A's appointment appears as an unrelated attachment."
      ]
    ],
    "question": "Which rubric condition is missing for each container, and can either be called fully ready from these records?",
    "answer": "Under PCA1, A lacks confirmed document release despite discharge and its own appointment in PCA2. B lacks an appointment despite discharge and release in PCA3; A's appointment does not satisfy B's container-specific requirement. Neither packet meets all three fictional conditions. Return the exact missing evidence and issuing-source scope instead of equating physical presence with pickup readiness or treating this document check as actual port authorization.",
    "failureModes": [
      "Treating discharge as sufficient availability despite another pending condition.",
      "Sharing one container's appointment across a different container's release packet."
    ],
    "fields": [
      [
        "Container and service date",
        "Defines the rubric target."
      ],
      [
        "Discharge, release and appointment states",
        "Separates conditions."
      ],
      [
        "Issuing source and unmatched attachment",
        "Supports the missing-evidence finding."
      ]
    ],
    "holdout": "Provide A's release effective day 3 while retaining its day-2 appointment. Require the date mismatch to remain before all conditions can match.",
    "boundary": "Use invented records and conditions. Exclude commercial parties, customs files and active schedules; partner ownership and operational decisions remain separate."
  }
}