{
  "title": "Marina slip reassignment records for AI",
  "source_page": "https://fiund.com/industries/marina-slip-reassignment-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A verified reassignment changes the allocation, not every stale booking label",
    "context": "Dummy bookings and slips form an offline allocation exercise. The packet contains no boats, berth map, access information or actual operating schedule.",
    "records": [
      [
        "MS1",
        "Practice booking B1",
        "Initially assigned slip S1. Request asks to move B1 to S2."
      ],
      [
        "MS2",
        "Authorized reassignment",
        "B1 to S2 effective day 4, approved by role R. Booking display still says S1 on day 5."
      ],
      [
        "MS3",
        "Other hold",
        "Slip S3 has an administrative maintenance hold. No hold names S1 or S2, and no physical readiness check is supplied."
      ]
    ],
    "question": "What allocation is documented for B1 on day 5, and what do the stale display or S3 hold establish about S2?",
    "answer": "MS2 authorizes B1's move to S2 from day 4, so it supports the day-5 allocation despite MS1's stale display value. MS3's hold applies to S3 only and does not change B1's documented assignment. Neither the allocation nor absence of an S2 hold establishes physical readiness, access or safety. Flag the booking-display mismatch while keeping those separate operational questions unresolved.",
    "failureModes": [
      "Using the stale booking display to ignore an authorized reassignment.",
      "Extending another slip's hold or inferring safety from an allocation record."
    ],
    "fields": [
      [
        "Booking and slip aliases",
        "Identifies the requested allocation."
      ],
      [
        "Approval and effective date",
        "Defines when the documented assignment changes."
      ],
      [
        "Display state versus authoritative event",
        "Preserves a stale-system discrepancy."
      ],
      [
        "Hold target",
        "Limits unrelated status events to their asset."
      ]
    ],
    "holdout": "Add a proposed move from S2 to S3 without approval. Require the model to retain the authorized S2 allocation while flagging the new request.",
    "boundary": "Use invented records. Exclude vessel IDs, owners, real berth layouts, financial data, access information and live schedules."
  }
}