visibility.cloud

Your first trace.
Here is exactly where it stands.

The worked trace below is rendered from the tested event model — the same corpus 1031/1031 conformance tests pass on — and the spine's stateless doors are live at epcis.dev today: translate, validate, hash. The answers layer — traces, custody evidence, partner grants — is entry-by-entry in a named entry in What ships today. No demo to sit through: the trace is on this page, and the seat list is on it too.

Beyond the worked trace, three more things you can do today, all real:

Answer ten questions instead of one.

The deeper door is the get-started interview: your address first, under the same promise, then a short sequence of questions that branch on your answers, ending in a written read for your situation. It locks when it ends, and if your segment is one we cannot serve it says so and stores nothing.

Get on the list for your side of the handoff.

One address and which side you are on — that is the whole form. The promise, in full: Your capture workspace is provisioned from this list. We write when your seat is ready, and follow up about it from there. We don’t sell your address or hand it to advertisers, and you can tell us to stop at any time. If we stop working on this, we say so rather than go quiet.

Which side of a handoff are you on?

One address, one row: what you type here — your address, the side you chose, and whichever of the two questions above you answer. We use your address to follow up about this. We don’t sell it or hand it to advertisers. What this site collects when you visit it, and what we do with it, are in the privacy policy. The named human sender and the verified sending address are a launch gate, recorded in this site’s What ships today; the message is not sent until both exist.

Look at the spine yourself.

epcis.dev is the same platform from the developer side: the capture interface, the schema validation, the event hash, the error bodies. Its translate, validate and hash doors answer over HTTPS today — the demo is a curl, not a call.

One row. Your capture workspace is provisioned from this list — we write when your seat is ready and follow up about it from there.

The dated ledger →

Your first trace, worked. One item, four handoffs, a who on every hop.

urn:epc:id:sgtin:0614141.107346.2017lot 7A-4412recordTime stamped by the gateway

  1. 05:41
    commissioning — line 3, a co-manufacturer's plant

    Lot 7A-4412 commissioned at the serial. who: human · line lead (attested)  ·  capturedBy: co-manufacturer account — the brand does not own this plant; the record still names who ran the line.

  2. 05:58
    packing — pack-out, same plant

    Cases aggregated to pallet sscc:…5501. who: human · pack-out  ·  capturedBy: co-manufacturer account

  3. 06:04
    receiving — DC west, the distributor

    Cold chain intact; the receiver is named in the record. who: human · dock crew  ·  capturedBy: distributor account

  4. 06:12
    receiving — the store back door

    The standard's own projection of this event validates against the official schema and says: a company received a case. The spine's record also says: who: human · crew member, on a handheld  ·  capturedBy: operator account. Two grains, never collapsed — and the party on every hop is derived at read time from grant chains, never stamped.

Illustrative — rendered from the tested event model, the same corpus the conformance tests pass on. Not customer data. A hosted trace exactly like this one is what the seat list on this page provisions toward. To take the same chain apart hop by hop — and switch the performer off to see which questions stop having answers — open One trace, two records.