Originary Verification Pilot
From signed records to a reviewable evidence case. Originary helps teams issue records at consequential workflow boundaries, verify supplied evidence under explicit key policies, and package the relevant artifacts for another organization, through a fixed-scope verification pilot.
- Issuer
- https://api.vendor.example
- Action
- POST /v1/market-data/search
- Policy
- terms:v3 sha256:4e21b8...
- Result
- 200 sha256:9a3c1d...
- Signature
- Ed25519 7d40e2c9...
Issue, verify, assess, hand off.
Four modules cover the full evidence path. Each works alone; together they turn a workflow into something another party can check.
Issue
Create a bounded signed record at the API, MCP, gateway, runtime, or payment boundary that directly observed the action.
Verify
Validate record structure, signatures, and disclosed-content bindings under a supplied key or an explicit expected-issuer policy.
Assess
Separate established claims from missing, conflicting, and unevaluated evidence.
Hand off
Export the records, native artifacts, verification results, and timeline for a customer, partner, auditor, or incident reviewer.
Evidence that outlives the system that made it.
What the recipient receives.
- case manifest
- selected PEAC records
- preserved native artifacts or references
- verification-key and issuer-policy information
- machine-readable verification results
- human-readable timeline
- established, missing, conflicting, and unevaluated findings
- integrity digests for the exported case
An evidence case is a product artifact. It is not a new PEAC wire type.
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 infrastructure, your keys, your records.
Open source is free and self-hosted. The verification pilot 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. |
| Verification pilot | Your infrastructure | Integration guidance, design, and support for the agreed engagement. |
| 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 |
One consequential workflow, implemented end to end.
The Originary Verification Pilot is a fixed-scope implementation engagement for one workflow, one issuer model, one verification path, and one external evidence recipient.
- workflow and trust-boundary map
- issuer and key-policy design
- working record issuance
- independent verification path
- one evidence-case export
- threat and non-issuance analysis
- deployment recommendation
Poem, Inc. is the Delaware corporation. Originary™ is its software and developer-tools brand. Originary Verify names the issue, verify, assess, and hand-off workflow that Originary implements through the Verification Pilot, built on PEAC Protocol: Apache-2.0 open-source software published and maintained by Originary that defines the record format and verification model. PEAC can be implemented and self-hosted independently, and verification does not depend on an Originary-hosted service.
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.