An overview of GS1 standards and their role in EPCIS 2.0 and the CBV

The gateway framing matters for this topic: epcis.dev accepts an event only after validating it against GS1's own schema, stamps the capturing account — capturedBy, the warrantor, kept distinct from who, the attested observer — identifies it by its CBV 2.0 hash, and appends it to a store nothing rewrites. What follows stands on those mechanics.

Start with the model. An EPCIS 2.0 event answers five questions about one observed moment: what objects were seen, when, where, why (the business step and disposition, drawn from the CBV — the Core Business Vocabulary), and how (sensor data, where instruments were involved). Events are captured over one standard interface, queried over another, and identified by the CBV 2.0 §8.9 hash of their own content. That is the whole standard in one paragraph; almost everything else is vocabulary, and the CBV is that vocabulary.

Custody is structural, not promised. No service identity holds an UPDATE or DELETE grant; the write path has exactly one writer and it can only append. You can add an event; you cannot un-write one, which is what makes a later trace evidentiary rather than merely stored.

Two attributions travel with every event, and the door owns a different half of each. capturedBy is the warrantor — the account whose key opened the door — stamped by the gateway together with recordTime and the attestation grade, with caller-supplied values in those stamped fields stripped. who is the attested observer, asserted by the caller and graded by the door: it reaches only the grade claimed until identity attestation lands. One is stamped, the other is graded; they never merge.

Provenance: an aged epcis.dev page, kept at its original URL and refreshed into the current design on 15 August 2026.

Proof, not adjectives. The gateway's conformance tests pass against GS1's normative artifacts, and the calculators answer on this origin — POST /translate, /validate, /hash, no key. The dated ledger is What ships today.