The evidence path for machine actions.
Originary Verify is the commercial product on top of PEAC Protocol: issue signed records where actions happen, verify them anywhere, and assemble evidence when someone asks what happened.
- Issuer
- https://api.vendor.example
- Action
- POST /v1/market-data/search
- Policy
- terms:v3 sha256:4e21b8...
- Result
- 200 sha256:9a3c1d...
- Signature
- Ed25519 7d40e2c9...
Record, Verify, Bundle.
Three modules cover the full evidence path. Each works alone; together they turn a workflow into something another party can check.
Record
Capture selected facts at the workflow boundary: what happened, which policy applied, what result was returned, when, and who issued the record. Sign it with your keys. Private logs never leave.
Verify
Check the signature, issuer, policy context, result, and bound digests independently. Strict offline with a supplied key, or explicit caller-authorized key resolution. No account, no callback.
Bundle
Assemble related records and supporting evidence into a portable bundle a counterparty, auditor, or procurement team can open and verify without access to your systems.
Evidence that outlives the system that made it.
One action, end to end.
- The issuer signed exactly these claims.
- The record was not changed after signing.
- Bound digests match the supplied content they cover.
- The record states which policy and result the issuer reported as applicable.
Verification establishes integrity and internal consistency of the supplied evidence. It does not independently prove omitted events or external real-world truth.
Your keys, your records, your infrastructure.
Open source is free and self-hosted. Supported self-host adds integration help under agreement, not a data hand-over.
| Mode | Where it runs | What Originary handles |
|---|---|---|
| Open source | Your infrastructure | Nothing. Apache-2.0 code, your keys, your records. |
| Supported self-host | Your infrastructure | Integration guidance, upgrades, and support under agreement. |
| Mode | Network | Use case |
|---|---|---|
| Strict offline | None. Record plus a supplied public key or JWKS. | Audit, air-gapped verification |
| Explicit resolution | Caller-authorized fetch of issuer config and JWKS. | Interactive tools and services |
| Cached resolution | Optional refresh under cache, expiry, and revocation policy. | Production verifiers |
A fixed-scope pilot, then scale.
The Originary Verification Pilot instruments one production workflow end to end in three to four weeks. Scope on the pricing page; records and solutions below.
Poem, Inc. is the Delaware corporation and Originary is its brand. Originary Verify is the commercial product; PEAC Protocol is the Apache-2.0 open-source protocol that defines the record format and verification model; the protocol works without Originary, and records verify without asking us.
Put a signed record on one workflow this week.
Start with the workflow another party already asks about. We will show what the signed record should contain.