RFID: which is better for supply chain traceability

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.

The same door answers people and agents. Capture, query, get_event, trace_epc 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.

Two attributions travel with every event, and neither is the sender's to assert. who is the attested observer; capturedBy is the account whose key opened the door. The gateway stamps both and strips whatever you sent in those fields.

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.