visibility.cloud

Containers.

A container is a reusable identity that outlives any one shipment, and its value leaks at the handoffs where nobody records who took it. visibility.cloud is built to keep the container on the record through every change of hands, so a returnable asset is accounted for rather than assumed lost.

Returnable transport items circulate between parties for years, and the recurring loss is a custody problem: the container left on a dock with no record of who has it. Each custody change is an event at the container's identifier, so the current holder is a query.

The same container carries a claim about its contents while it is loaded and stands as its own tracked identity while it is empty.

← What moved

The envelope, at the custody change a returnable asset usually loses.

{ "bizStep": "receiving", "disposition": "in_progress", "epcList": ["urn:epc:id:grai:0614141.54321.T-0088"], "eventTime": "2026-07-30T06:12:04Z", "recordTime": "(stamped by the gateway — the sender cannot set it)", "who": { "kind": "human", "role": "yard coordinator", "grade": "attested" }, "capturedBy": "(3PL account — the warrantor account whose key opened the door)", "party": "(derived at read time from grant chains — never stamped)" }

The GRAI outlives any one shipment; the current holder is then a lookup, not an assumption. Illustrative — rendered from the tested event model, the same corpus the conformance tests pass on. Not customer data, and not a customer's record: a worked figure in the record's own grammar.

See your first trace.

Capture workspaces for 3PLs and cross-docks are provisioned from the seat list — we write when your seat is ready.