# Conformance — conformant is a digest you can check

Every document is validated against the official GS1 EPCIS 2.0.1 JSON schema — pinned by sha256, precompiled, eval-free — so "conformant" is a digest you can recompute, not a word we chose.

Check it from here: POST /validate on this origin takes any EPCIS 2.0 document or event and answers with the verdict and per-path errors against the pinned schema — no key, no account. **No conformance attestation has ever been issued**, by us or about us. A signed run requires a hosted registrar and a named human Registrar, and the registry code refuses unsigned publication by construction.

## The pins

| artifact | role | sha256 | retrieved |
|---|---|---|---|
| openapi.json | REST binding shapes (Capture + Query interfaces) | 3d33792c520d7a7a1d080382d956730bb07021c7dd1cc17229fce27b784d66fc | 2026-07-19 |
| epcis-json-schema.json | document/event validation — the projection-invariant schema | 0f46ff694efffd8d8ce840a33dfde84228add11b516b8b258f3200740ae210af | 2026-07-19 |
| epcis-context.jsonld | JSON-LD expansion checks | 5056c65f991425b1d3a35e35edf4f7d0c7ff56cf688c2912b930f93494713737 | 2026-07-19 |
| query-schema.json | SimpleEventQuery validation | 4b5583c9a0a715324594617f3cf6744f4f930568484f7df8fb7aa81819355341 | 2026-07-19 |
| epcis-shacl.ttl | semantic-graph validation (secondary) | 7db2547a7a55e7d6e6f19c0ad472d1f0987ef19f3d04a43b195bca55c0cc7f42 | 2026-07-19 |

Pins change only by journaled human ruling; pnpm verify:pins re-checks the digests in CI. Retrieve the same artifacts from ref.gs1.org and hash them yourself. GS1 has not reviewed, certified or endorsed this project.

## The advisory suite

Suite version 0.4.0, verdict logic 0.3.2, 18 checks, pinned to the GS1 EPCIS repository at commit 2b888befbc071e1c2d388e027b30149b3f51dcef. The GS1 repository publishes exactly 2 test-case-requirement documents (TCR-53, TCR-54); the Mandatory Requirements Matrix references TCR-43, which has no published document. Every CLI run is marked advisory, and the CLI never signs. Errors ship as RFC 7807 application/problem+json carrying the standard's own exception types.