Written for the VP / Senior Director of Supply-Chain Traceability — the programme office that owns a funded Sunrise 2027 plan, a vendor shortlist, and, increasingly, the tooling that reads the shortlist before any human does.
The quiet change in enterprise procurement is not that agents negotiate. It is that agents read first. A programme office deputizes an agent with a mandate ceiling and a checklist; the agent sweeps the candidate vendors' surfaces; and what comes back to the human is not impressions but matches — this vendor's claims resolved to checkable facts, that vendor's claims resolved to nothing, because there was nothing machine-checkable to resolve them against.
An agent can check artifacts. It cannot check adjectives. That single asymmetry is about to reprice every vendor page in this category.
The checklist, published — run it on anyone, including us
Here is what a procurement-class agent evaluating a traceability record layer can actually verify, item by item, with what a pass looks like. Every row is either machine-checkable or it is not; there is no partially.
| Checklist item | Machine-checkable form | What claims-only copy offers instead |
|---|---|---|
| Standard conformance | The pinned spec version, named: EPCIS 2.0 / CBV 2.0, validated against GS1's official JSON schema | "fully standards-compliant" |
| Schema provenance | sha256 digests of the vendored GS1 artifacts, re-checked in CI | "built on GS1 standards" |
| Translation fidelity | A per-job round-trip fidelity report the agent can parse | "seamless migration" |
| Event identity | The CBV 2.0 §8.9 event hash, gated against OpenEPCIS reference vectors — someone else's answers, not the vendor's own | "tamper-proof records" |
| Error behavior | RFC 7807 problem+json carrying the standard's own exception types | "robust validation" |
| Live behavior | Doors that answer over HTTPS to a probe the agent sends itself | a demo, scheduled through a human |
The developer-side artifacts behind the left column are exercisable at epcis.dev: translate, validate, and hash answer over HTTPS, against sha256-pinned official GS1 artifacts, and the agent needs no meeting to confirm any of it. The machine-readable statements of who this platform serves and what an agent may do here are published documents on this origin — /icp.json, /agent-classes.json, /flow.json — because a surface that expects agent readers owes them structure, not prose scraping.
The hash row is the deepest one: an event identity computed from content, matched against reference vectors maintained outside our walls, is what lets a counterparty verify a record without joining anything — the flagship argument is Verifiable without joining.
Score a claims-only vendor page against that checklist and the result is not a low score. It is an empty score — no pinned version to match, no digest to verify, no vector set to replay. To the human eye the page reads as confident. To the evaluating agent it is invisible, in the precise sense that nothing on it can enter a comparison.
The ceiling is a feature, and it works for you
A deputized procurement agent operates under a mandate ceiling its human authored — see what a seat actually is. When an ask exceeds the ceiling, the agent does not improvise; the decision returns to the programme office. And here is the part worth noticing: an agent that has already verified value inside its mandate — translated a corpus, validated a sample, matched hash vectors — comes back to you as an internal witness carrying realized results, not a vendor's claim. The strongest advocate in your next steering meeting may be your own tooling, reporting what it checked.
That is also why the fail-closed rule matters at evaluation time: an agent that cannot reach its human when it hits a gated scope does nothing, loudly, and the refusal is recorded. A vendor whose agent surface silently grants what should have escalated has just failed the evaluation in the most informative way possible — the argument in full is No silent grants.
What this means for your programme plan
Your Sunrise 2027 programme office has already made the mark decisions the calendar demanded — the symbology, the URI form, the artwork sequencing under the brand-owner read. The event-layer decision that remains is the one your evaluation tooling will make legible: which record layer's claims survive contact with a checklist that cannot be charmed.
So the request to make of every vendor in the shortlist — now, before the agent sweep, so the sweep has something to find — is one sentence: "Send the machine-checkable version of every claim in your deck." The pinned versions. The digests. The reference vectors. The error bodies. The endpoint a probe can hit. Vendors who have them will send them in an hour. Vendors who do not will send a meeting request, and that is also an answer.
We publish ours as the checklist above precisely because the discipline cuts both ways: run it on us first.
When the programme plan is ready to name a repository, start the interview — it asks about your estate and your clocks, and it ends with exactly one promise about contact.