One proof grammar.
Controlled upgrade layers.
PlenaProof now names the layers it already needs: simple receipts first, stronger evidence packets when facts matter, public registry and QR verification when recipients must check status, and AI-era trust receipts when machines are involved.
PLENA's VRX stack is now explicit.
PlenaProof uses VRX-1 for basic proof receipts, VRX-2 for evidence packets, VRX-4 for public registry / QR verification, and VRX-5 for AI-era trust receipts.
Controlled upgrade rule
VRX-1 remains the foundation. Higher VRX layers do not replace it; they extend the same receipt grammar only when the case needs stronger evidence, public interoperability, or AI-era accountability. This keeps the consumer experience simple while allowing institutions to adopt stronger proof standards.
| Layer | PLENA role | Primary buyer/user value | Current d19.131 asset |
|---|---|---|---|
| VRX-1 | Basic proof receipt | Someone can read and review the core record without needing PLENA's internal database. | Existing VRX-1 pages and universal receipt schema. |
| VRX-2 | Evidence packet | A scattered case becomes a structured packet with attachment references, custody events, redactions, and export trail. | vrx2-evidence-packets.html + assets/vrx2-evidence-packet.schema.json. |
| VRX-4 | Public registry / QR verification | A recipient can scan or open a verification route and inspect public-safe receipt status. | vrx4-public-registry-qr.html + assets/vrx4-public-registry-record.schema.json. |
| VRX-5 | AI-era trust receipt | AI-assisted decisions become reviewable: who used AI, who reviewed it, what risk flags existed, and what appeal route remains. | vrx5-ai-era-trust-receipts.html + assets/vrx5-ai-trust-receipt.schema.json. |
Start with a simple receipt
A user should not need to understand all VRX layers. The interface can ask what happened, gather evidence, and choose the appropriate layer behind the scenes.
Upgrade only when needed
Institutions can request VRX-2 for evidence-heavy cases, VRX-4 for public verification, and VRX-5 for AI-assisted workflows.
No fake certification
The standard distinguishes local/static verification, public-safe registry publication, and any future cryptographic or partner-backed confirmation.