{
  "title": "Marine cargo handling data for AI tally reconciliation",
  "source_page": "https://fiund.com/industries/marine-cargo-handling-tally-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Two scan locations and a duplicate event can still describe one handled unit",
    "context": "A synthetic vessel-to-staging sequence uses generic objects and original scan cards. There is no live lifting, terminal equipment, commercial manifest or real cargo-security information.",
    "records": [
      [
        "MT1",
        "Unit U1 scans",
        "Shipment S-A/U1 observed at discharge point, then staging point. Staging event E2 duplicated with the same event key."
      ],
      [
        "MT2",
        "Confirmed tally",
        "Supervisor's original mock tally confirms distinct units S-A/U1 and S-A/U2 discharged. U2 has one exact matching discharge scan."
      ],
      [
        "MT3",
        "Loose scan",
        "S-B/U3 has the same last characters as S-A's shipment label but is a distinct shipment. No S-A/U3 tally or exact scan supplied."
      ]
    ],
    "question": "Which distinct S-A units are supported, and why cannot the raw scan total establish another handled unit?",
    "answer": "MT1 and MT2 support two distinct S-A units, U1 and U2, matching the supervisor tally. U1's scans at successive locations and duplicated E2 remain observations of the same unit. MT3 belongs to shipment S-B and cannot create an S-A/U3 record from suffix similarity. Count unique shipment/unit identities with event provenance rather than sum scans or treat every location observation as another discharged item.",
    "failureModes": [
      "Counting repeated scans or location transitions as additional cargo units.",
      "Joining shipment records by matching suffixes instead of full identity."
    ],
    "fields": [
      [
        "Full shipment and unit ID",
        "Defines unique cargo props."
      ],
      [
        "Scan point, time and event key",
        "Supports sequence and deduplication."
      ],
      [
        "Supervisor tally and missing exact match",
        "Provides independent review context."
      ]
    ],
    "holdout": "Add an S-A/U3 staging scan without discharge confirmation. Require its presence to be acknowledged while discharge status remains unsupported.",
    "boundary": "Use props, synthetic records or separately cleared stills. Exclude real markings, manifests and operating equipment footage."
  }
}