EPCIS and the Role of Machine Learning in Supply Chain Automation

EPCIS 2.0 is the GS1 standard for supply-chain event data, and epcis.dev is a capture gateway for it: post an event and the door validates it against GS1's own schema, stamps who captured it, hashes it by CBV 2.0, and appends. That is the ground the topic above stands on.

Reads are minimally scoped. You see your own scope; what is outside it is absent, not greyed out and not redacted, so there is no shape left behind to argue about. Recording an event is $0 by policy, because a stream that charges per event is one you stop feeding the month the bill grows with volume.

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.

Build state, 29 July 2026. The capture gateway is written and its conformance tests pass against GS1's normative artefacts. Nothing is hosted yet: there is no public endpoint, no key to hold, and no account to open. Today the interface answers on your own machine under wrangler dev; the full ledger is at What ships today.