Proof journeys make PLENA instantly understandable: a person or institution chooses a real situation, follows a short path, produces a binder or receipt, and receives a wallet-ready verification record.
Each journey begins with a concrete anxiety: “I need to prove this happened,” “I need to preserve this,” or “I need a human to review this.”
| Institution | First PLENA use | First receipt | Operational output |
|---|---|---|---|
| University registrar | Credential issuance or transcript-status proof | Credential receipt with scope, issuer, and verification URL | Registrar pilot binder and first issuer profile |
| NGO / humanitarian office | Field-service occurrence or beneficiary proof packet | Human-service receipt with privacy-preserving summary | Donor/auditor evidence binder |
| Church / ministry office | Membership, service, safeguarding, or pastoral-care record | Institutional attestation receipt with strict boundaries | Protected institutional evidence file |
| Publisher / journal | Human authorship, peer-review path, or correction record | Authorship/provenance receipt | Editorial proof packet |
| Human services agency | Provider attendance, consent, and service occurrence | Human-presence receipt with complaint route | Service audit trail |
PlenaProof asks: “What happened, who needs to believe it, and what can safely be shown?” Every journey routes from those three questions to the platforms that answer them.