{
  "title": "Passenger vessel boarding and transfer counts for AI review",
  "source_page": "https://fiund.com/industries/passenger-vessel-boarding-count-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Reservations, corrected boarding and intermediate transfers use different count bases",
    "context": "A fictional two-leg journey uses artificial aggregate counts only. There is no manifest, vessel, crew, access detail, live sailing or departure decision.",
    "records": [
      [
        "PVB1",
        "Leg 1 plan",
        "Reservations 20, canceled reservations 2. These are booking records, not observed boarding."
      ],
      [
        "PVB2",
        "Boarding and correction",
        "Initial leg-1 boarding 17; approved correction explicitly replaces it with 18. At intermediate stop, confirmed 3 leave and 2 board."
      ],
      [
        "PVB3",
        "Other transfer note",
        "Proposed additional transfer of 1 has no completed event. No other movements under this fixture's stated count rule."
      ]
    ],
    "question": "Which counts are supported at initial boarding and after the confirmed intermediate events, and can the proposed transfer change them?",
    "answer": "PVB2 sets corrected initial boarding at 18, replacing the original 17 rather than adding another boarding group. Confirmed intermediate events yield 18 minus three plus two, or 17 onboard in the fictional count model. PVB3's proposed extra transfer lacks completion and cannot change that observed-event total. PVB1's reservations describe a different state. Preserve all bases without inferring real passenger identity, safety capacity or permission to depart.",
    "failureModes": [
      "Using reservations as observed boarding or double-counting original and corrected totals.",
      "Applying a proposed transfer as if completed or assuming every leg retains all passengers."
    ],
    "fields": [
      [
        "Journey leg and count type",
        "Defines the quantity."
      ],
      [
        "Boarding correction and replacement target",
        "Preserves the current count."
      ],
      [
        "Confirmed transfer event and proposed state",
        "Supports interval reconstruction."
      ]
    ],
    "holdout": "Add an intermediate event for another journey with the same stop label. Require the journey mismatch to prevent changing this count.",
    "boundary": "Use synthetic aggregates and original records. Exclude manifests, staff and current sailing information; qualified staff retain all vessel decisions."
  }
}