The first issuer should not be asked to adopt everything. The pilot kit offers one controlled workflow: a defined receipt type, a small cohort, a review path, public-safe verification, and a simple outcome report.
A serious issuer wants clarity, liability boundaries, workload limits, and a visible benefit.
Registrar, NGO trustee, publisher, church office, employer, legal-aid office, or human-services agency.
Credential status, service occurrence, authorship provenance, records intake, staff review, or beneficiary evidence.
Start with 5–25 records, not the whole institution.
Use one VRX-1 receipt family with clear public limits and private evidence boundaries.
Identify use case, issuer authority, records owner, privacy boundary, reviewer role, and pilot success metric.
Build the binder template, claim map, sample receipt, and verification-result mockup.
Issue sample or controlled receipts for the small cohort. Keep strong claims off until legal and technical checks are done.
Summarize friction, time saved, evidence quality, refusal rate, user clarity, and next production requirements.
| Deliverable | What it contains | Why it sells |
|---|---|---|
| Issuer profile | Name, role, authority, contact, workflow scope, pilot status. | Creates a visible adoption signal. |
| Evidence binder | Claim map, source inventory, reviewer notes, refusal/correction route. | Gives staff a repeatable operating file. |
| Sample VRX-1 receipt | Receipt ID, issuer, claim, scope limit, verification URL. | Makes the abstract protocol tangible. |
| Public verification result | Narrow public summary with privacy boundary. | Shows the end-user experience. |
| Pilot report | Outcome, objections, risks, next technical steps, price path. | Creates a follow-up conversation. |