EPCIS 2.0 and the CBV for optimized supply chain decision making

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.

The concrete gain is evidentiary, not cosmetic. Events validated at capture cannot drift from the standard; the CBV §8.9 hash makes a duplicate the same event and an edit a different one; and an append-only store means the answer to a later dispute, recall or audit is a chain of records that nobody — including the operator — could rewrite. The cost that disappears is the reconciliation meeting.

The same door answers people and agents. Capture, query, get_event, trace and translate are exposed over MCP, so a logistics agent captures and queries with the same key a person would use, without a human copying values between two systems.

The part epcis.dev makes concrete is validation. Every event is machine-checked against the official GS1 EPCIS 2.0 JSON schema before it is accepted, and a capture that does not validate is refused as application/problem+json carrying the standard's own exception types, not a vendor error string.

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