This page turns PlenaProof from a polished concept into an onboarding path: who can issue, what they can issue, what must be reviewed, and how a first pilot can stay legally and operationally modest.
The first issuer should not be the biggest possible institution. It should be the most reachable credible institution.
A registrar, director, bishop office, trustee, editor, HR lead, or program manager can approve a small pilot.
Start with one limited receipt: attendance, credential submission, editorial provenance, human review, service receipt, or refusal receipt.
Receipt confirms a record or action; it does not overclaim identity, legality, professional quality, or government recognition.
A PLENA pilot can begin as a controlled receipt workflow with no public database exposure. The issuer may export a VRX-1-like receipt, verify a limited public-safe ID, and keep all sensitive records inside its own files until a production backend is approved.
Do not call an institution an active issuer until they have explicitly agreed and the authorized scope is documented.
| Question | Why it matters |
|---|---|
| What kind of institution are you? | Routes the buyer to university, church, NGO, publisher, employer, government, travel, mobility, or human-service workflows. |
| Which receipt do you want first? | Keeps the pilot narrow and testable. |
| Who has authority to issue? | Prevents anonymous or unauthorized receipts. |
| What must stay private? | Protects confidential records and reduces legal risk. |
| What should a third party be able to verify? | Defines the public verification surface. |
Most institutions will not build VRX-1 issuance themselves. A hosted portal is the bounded product: issue, revoke, correct, verify, and export audit logs.