PLENA Verification Methodology

Verification is a ladder, not a magic stamp.

PLENA’s method separates readable structure, evidence readiness, issuer confirmation, and signed production verification. This protects trust by avoiding overclaiming.

Verify a receiptReceipt schemaVRX-1 standard

Five verification levels

Each level answers a different question. Public verification can be open, but higher-confidence creation and management can remain paid or institutional.

L0 · Link or ID format check

Does the receipt ID or QR link have a recognizable PLENA/VRX-1 pattern?

L1 · Schema conformance

Does the receipt include the required public fields: protocol, receipt ID, issuer, type, timestamp, status, privacy level, and sharing mode?

L2 · Evidence-readiness review

Does the receipt point to evidence references, human actions, source checks, or next-step documentation without exposing unnecessary private data?

L3 · Issuer or registry confirmation

Does a trusted registry or issuer endpoint confirm that the receipt exists, is not revoked, and matches public metadata?

L4 · Signed, sealed, or audited verification

Does production infrastructure confirm hash/signature, issuer key, audit log, revocation status, and permission scope?

Public method

  • Show the receipt type and claim plainly.
  • Inspect the selected receipt only; do not imply access to hidden databases.
  • Flag missing fields as missing, not fraudulent.
  • Distinguish structural validity from authenticity.
  • Keep revocation, expiration, issuer keys, and registry checks explicit.

Commercial method

  • Charge for creating, managing, preserving, and exporting certified receipts.
  • Offer institutional dashboards, batch workflows, staff roles, procurement packs, and audit reports.
  • Keep public verification open enough that recipients trust the receipts.
  • Reserve high-assurance verification for production registry and signed receipt services.

Applied across PLENA

The same ladder can support individuals, institutions, and central services without turning every page into a database.

WorkflowReceipt questionLikely level
PlenaProof VaultCan this person share a readable proof profile and selected receipt timeline?L1–L2 preview, L3–L4 later
AI OversightCan the institution show human review of an AI-assisted decision?L2 now, L3–L4 production
Agent ReceiptsCan a user show what an AI agent did and whether a human approved it?L1–L2 preview
ORIGINACan a creator or founder show priority, authorship trail, contract, or NDA record?L2 with future L4 signing
PROVACan a person or institution show evidence readiness and action history?L2 with registry option
SIGILLACan a sealed packet show routing, custody, and selected verification status?L2–L4 depending on deployment