Receipts travel.
Databases stay home.
VRX-4 is the interoperability layer PlenaProof uses when a recipient needs to scan, open, or inspect public-safe receipt status without receiving the entire underlying case file.
VRX-4 makes receipts interoperable.
VRX-4 is the public registry and QR verification layer: public-safe registry records, issuer references, revocation status, related receipt links, and machine-readable trust levels.
Scan to inspect
A QR code or receipt URL should lead to a public-safe verification page showing status, issuer, type, timestamp, and boundaries.
Verify without oversharing
The public record can confirm metadata and status without exposing the private file, underlying evidence, or full case database.
Receipts travel
VRX-4 gives external institutions a stable way to read a PLENA receipt and understand its trust level and verification route.
| VRX-4 component | Purpose | Truth boundary |
|---|---|---|
| public_registry_id | Stable handle for a public-safe receipt record. | Does not expose private evidence by default. |
| qr_verification_url | Human and machine-readable verification route. | Static/local preview unless backed by a live registry service. |
| issuer_registry_ref | Connects a receipt to an issuer profile or organization record. | Issuer authority must be separately verified. |
| revocation_status | Shows active, superseded, revoked, expired, or disputed status. | Status visibility depends on registry publication. |
| trust_level | Machine-readable tier such as local, registry-listed, issuer-confirmed, or externally anchored. | No claim of blockchain or government verification unless actually implemented. |
PLENA routing
VRX-4 strengthens Public Verify, the open registry pages, QR proof profiles, public hash manifests, issuer networks, organization registry, and wallet verification links.
Schema anchor
assets/vrx4-public-registry-record.schema.json receipts/PLENA-DEMO-VRX4-20260516-001.json