The Trust Operations pack translates PLENA’s proof theory into practical operating procedures: who receives evidence, who reviews it, who issues receipts, what gets refused, how users verify, and how the first issuer pilot can be run without overclaiming.
PLENA aims to feel simple to a user and disciplined to an institution. This manual defines the minimum trust operations needed before larger sales, standards work, or mobile deployment.
Map each user or institution to a concrete journey instead of asking them to understand all 14 platforms first.
2Use sample VRX-1 receipts to show what PlenaProof records, what it does not prove, and how public verification should read.
3Organize claims, documents, reviewer notes, refusal reasons, receipt IDs, and public verification links into one defensible packet.
4Offer one institution a narrow first pilot: one workflow, one cohort, one receipt type, one review path, one measurable outcome.
5Define reviewer scope, training, oath language, conflict rules, complaint paths, and escalation limits.
6Show the user exactly what a verified, limited, expired, revoked, or review-needed receipt result should look like.
7Support institutions and communities whose first real channel is WhatsApp, not a portal login.
8Give the founder usable letters for registrars, NGOs, churches, publishers, legal aid offices, insurers, and human-service organizations.
| Function | Minimum rule | Why it matters |
|---|---|---|
| Intake | Collect summaries first. Avoid sensitive raw documents in public pilot forms unless a secure backend exists. | Prevents accidental overcollection. |
| Evidence binder | Separate claim, source, reviewer observation, issuer action, public verification, and private files. | Makes PLENA legible to institutions and counsel. |
| Review | Every human review must have reviewer identity, scope, timestamp, limits, and conflict-of-interest status. | Turns “human review” into accountable infrastructure. |
| Refusal | A refusal should be recordable without humiliating the user or exposing private evidence. | Refusal is part of trust, not failure. |
| Issuer pilot | Start with one issuer, one workflow, one cohort, and one receipt type. | Converts PlenaProof from brochure to adoption path. |
| Wallet | Wallet v1 should store and share receipt summaries, verification links, QR codes, and export packets. | Creates individual habit and proof portability. |
When in doubt, PLENA makes a narrow, verifiable claim rather than a broad impressive claim. “This institution issued receipt X for claim Y on date Z under scope Q” is stronger than “this person is verified.”
Use the Trust Operations pack to approach one serious institution with a concrete pilot kit, sample receipts, sample verification result, and an evidence binder template. The goal is not a perfect platform; the goal is a first real issuer workflow.