Shipments.
A shipment is a consignment with a beginning and an end and a custody chain in between, and the disputes live in the between. visibility.cloud is built to close that chain hop by hop from dispatch to receipt, so the shipment's path is a sequence of attested events rather than two endpoints and a guess.
The dispatch notice says who sent and the receipt says who took delivery; both are silent on the carriers and cross-docks in the middle. The spine records the place, the time, the business step and the attested observer at each seam — the party at every hop is derived at read time from grant chains, never stamped — so the middle exists on the record.
The consignment associates with the packages and units inside it, so a claim about contents travels with the shipment and can be checked at receipt.
The consignment, seam by seam: two endpoints everyone records, and the middle only an event can hold.
consignment urn:epc:id:sscc:0614141.0000005501recordTime stamped by the gateway
-
09:10
shipping — dispatch, the sender’s dock
The endpoint every dispatch notice records — now with an observer. who: human · outbound lead · capturedBy: shipper acct
-
13:22
arriving — the cross-dock in the middle
The stretch both endpoint systems are silent about, on the record. who: human · dock crew · capturedBy: 3PL acct
-
16:48
receiving — the receiver’s door
The claim about contents, checked at receipt against the aggregation events it traveled with — and the party at every hop derived at read time, never stamped.
See your first trace.
Capture workspaces for carriers are provisioned from the seat list — we write when your seat is ready.