Bind
Bind one customer-nominated synthetic release, evidence set, audience, action and decision into a signed receipt.
Agent Trust Infrastructure · In pilot
One release. One evidence set.
One signed decision.
The Signed Release Decision Receipt binds an exact release, the evidence used to assess it and the resulting decision into a receipt designed for offline verification.
In pilot · application only · not for production reliance
ONE RELEASE. ONE CONNECTED RECORD.
01 / RELEASEThe exact build or configuration
A fingerprint of the artifact being assessed.
02 / EVIDENCEThe exact evidence set
The checks and results tied to that same release.
03 / DECISIONThe signed gate decision
A bounded decision that can be verified offline.
Designed to fail closed when the receipt or its status evidence changes.
What the pilot can demonstrate
Verify the approved bundle. Reject the wrong one.
Verify
Use a pinned public key to verify the exact approved bundle offline without calling a hosted Veyran service.
Fail closed
Demonstrate machine-readable rejection of altered, expired, revoked, superseded, malformed or stale evidence.
Our private verifier currently passes 32 of 32 synthetic cases spanning valid receipts, tampering, wrong audience or action, expiry, revocation, supersession and stale or forged status snapshots.
Synthetic prototype evidence—not a customer result, certification, public registry, production credential or claim that the underlying release is safe.
Design-partner evaluation
Start narrow, then earn the right to broaden.
No production access, customer data or secrets are required for the initial evaluation.
- Step 01
Nominate
Choose one synthetic release decision where artifact, evidence and approval need to stay connected.
- Step 02
Freeze
Agree the receipt contract, verifier inputs, rejection cases and evaluation success test.
- Step 03
Demonstrate
Veyran produces the signed receipt and offline verification evidence for the agreed scenario.
- Step 04
Decide
Receive the input/output contract, evidence and a frank production-gap report before any broader commitment.
Honest boundaries
A cryptographic signature answers only part of the trust question.
The pilot can show whether a receipt is cryptographically intact and whether its current status evidence meets the agreed policy. It does not prove the software is safe, the tests are sufficient or the claims are true.
Production key protection, rotation and recovery, cross-language canonicalisation, independent security assurance, interoperability and issuer trust remain open production gates.
Apply for the pilot
Where does your release evidence break apart?
Write with one synthetic release scenario, who needs to verify the decision and what must fail closed. We will confirm fit, scope, success test and a fixed quote before any work begins.
- hal@veyran42.co.uk
- Subject
- Release Receipt pilot
- Status
- In pilot · application only
- Production use
- Not authorised