Computer Hardware.
Gray-market diversion and warranty fraud are custody problems wearing another name. visibility.cloud is built to record who held each serialized component at every handoff, so a diverted unit is a gap on the record rather than an argument between two systems.
Every unit was scanned. The investigation still ends at “seen here, then not.”
The marginal information left in a fully-instrumented chain is not another read point — you already have the read points. It is a witness: which person, which system, observed the unit at the moment it went sideways. That is the one thing the standard has no field for, and the one thing a diversion investigation actually needs.
Drives, boards and modules move through distributors, integrators and cross-docks before they reach a chassis. Each is identified down to the serial; the spine records the read point, the time, the business step and the attested observer at every link — the party at each hop is derived at read time from grant chains, never stamped — so the provenance of a specific unit is answerable rather than inferred from a purchase order.
Every event is validated against the official GS1 EPCIS 2.0 JSON schema on capture and identified by the CBV 2.0 §8.9 event hash, so the same unit's history is stable across every system that records it.
The envelope, at the outbound dock: one serialized drive, one attested observer.
{ "bizStep": "shipping", "disposition": "in_transit", "epcList": ["urn:epc:id:sgtin:0614141.300551.SD91-4407"], "eventTime": "2026-07-30T06:12:04Z", "recordTime": "(stamped by the gateway — the sender cannot set it)", "who": { "kind": "human", "role": "outbound dock lead", "grade": "attested" }, "capturedBy": "(distributor account — the warrantor account whose key opened the door)", "party": "(derived at read time from grant chains — never stamped)" }
See your first trace.
Capture workspaces for manufacturers and brands are provisioned from the seat list — we write when your seat is ready.