visibility.cloud

Logistics & 3PL.

The traceability clause you answered softly last time — a description of your WMS and a paragraph about SOPs — can be answered hard. Custody is your product, and the standard record of a custody change has no place to name who took it.

Verified 31 July 2026. The spine behind this page passes 683/683 conformance tests against GS1's normative artefacts, and its translate, validate and hash doors are live at epcis.dev. Every open gap is a named entry in the open P0 ledger; the dated summary is at What ships today.

The dock is where custody actually changes hands and where the record goes silent on the performer: five dimensions, no performer, party fields at organisation grain. On a shift where a meaningful share of the labour is agency or temp, that is the whole problem in one sentence. The spine's record names the attested observer at every handoff — including the embodied one: a robot or an autonomous reader on your dock is attested the same way a person is, and it is never confused with the account that warrants the capture.

Capability here wins tenders — revenue logic, not compliance. A SharingGrant answers the clause with a grant instead of a paragraph: exactly these goods, these event kinds, this window, at this attribution grain, enforced identically on every read and revocable without rewriting history — because the party on an event is derived at read time from grant chains, never stamped, a record made under one client contract survives that contract ending. The grant object carries a named entry in the open P0 ledger; the scope engine it compiles to is written and verified.

← Who held it

One shift at the dock, on the record: agency labour and an autonomous reader, attested alike.

pallet urn:epc:id:sscc:0614141.0000005501recordTime stamped by the gateway

  1. 14:02
    arriving — inbound, door 9

    A temp on his third shift takes the handoff, and the record can say so. who: human · agency dock crew  ·  capturedBy: 3PL acct

  2. 14:07
    observing — autonomous MHE, staging lane

    The embodied observer: a machine on the dock is attested the same way a person is, and never confused with the account that warrants the capture. who: thing · AMR-11 (id.org.ai)  ·  capturedBy: 3PL acct

  3. 17:40
    shipping — outbound to the client’s DC

    Custody closes with a named observer on the closing event — and the party at every hop is derived at read time from grant chains, never stamped, so the record made under this contract survives the contract ending.

This strip is what a SharingGrant scopes a shipper into — the grant object's ledger entry is named above. 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, in order — one email when your seat is ready.

We answer in writing. We take at most five conversations a month, only when you ask for one, and only after you already have the written read.