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 683/683 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 the open P0 ledger. No demo to sit through: the trace is on this page, and the seat list provisions in order.

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 one-message 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, in order. One email when your seat is ready — one, not a drip campaign. Nothing else, ever — no newsletter, no sequence. If we stop working on this, you get one message saying so and your address is deleted. Either way it is one message.

Which side of a handoff are you on?

One address, one row, write-only; the list lives on this origin and goes nowhere else. The named human sender and the verified sending address are a launch gate, recorded in this site’s open P0 ledger; the message is not sent until both exist.

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.

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, in order. Your capture workspace is provisioned from this list — one email when your seat is ready, one, not a drip campaign.

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.