{
  "title": "Pilotage and tug service records for AI event matching",
  "source_page": "https://fiund.com/industries/marine-pilot-tug-event-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Pilot boarding, tug acknowledgment and vessel movement are distinct call events",
    "context": "An original two-call simulation uses fictional service roles and abstract time references. It includes no vessel, personnel, harbor procedure, route or navigation instruction.",
    "records": [
      [
        "MPT1",
        "Call A records",
        "Pilot boarding confirmed 08:00; later authorized correction changes that service time to 08:05. Tug request acknowledged 08:00, no tug-arrival event."
      ],
      [
        "MPT2",
        "Call A movement",
        "Separate original movement event confirmed 08:20 for A. It does not state tug arrival or readiness."
      ],
      [
        "MPT3",
        "Call B",
        "Same planned service time 08:00. Pilot request accepted, no boarding or movement. No A-to-B identity relationship."
      ]
    ],
    "question": "Which A milestones and corrected time are supported, and can its movement or B's matching plan establish the other service events?",
    "answer": "MPT1 supports A's pilot boarding at corrected 08:05 and a separate tug-request acknowledgment. MPT2 documents A's 08:20 movement without confirming tug arrival. MPT3 supplies only accepted pilot request for B; its matching planned time cannot inherit A's boarding or movement. Keep call identity, role, event type and correction scope together rather than use one milestone as proof of another service's readiness.",
    "failureModes": [
      "Treating tug acknowledgment as arrival or movement as proof of every support service.",
      "Propagating one call's corrected pilot time to another call sharing its plan."
    ],
    "fields": [
      [
        "Call and service role",
        "Defines the event."
      ],
      [
        "Planned/acknowledged/boarded/movement type",
        "Separates milestones."
      ],
      [
        "Correction parent and effective time",
        "Preserves the current source."
      ]
    ],
    "holdout": "Add B's boarding confirmation in an unknown time zone. Require occurrence to resolve while precise cross-call timing remains unverified.",
    "boundary": "Use original offline records and a limited rubric. Exclude harbor communications and access points; no output directs navigation."
  }
}