The VRX receipt structure your platforms can emit and consume. Map fields to your existing records, audit logs, and case-management systems for standards-aligned interoperability.
Every PLENA receipt follows one simple, shared structure, so it can be checked anywhere. You do not need the technical details to use it — this page explains what is inside, in plain terms.
VRX-1 gives PLENA receipts a common shape so a person, institution, auditor, or recipient can understand what was created, who issued it, what it claims, and what still requires confirmation.
The schema is intentionally modest. A receipt should not expose private databases. It should expose enough selected facts for verification, routing, citation, and audit.
| Field | Purpose | Required? |
|---|---|---|
| protocol | Identifies the public standard, normally VRX-1. | Yes |
| schema_version | Shows the schema version used to generate the receipt. | Recommended |
| receipt_id | Stable, citable identifier for the selected receipt. | Yes |
| issuer | Entity or PLENA workflow that issued the receipt. | Yes |
| receipt_type | Human review, agent action, proof packet, origin record, evidence record, seal, credential-readiness record, or wallet archive marker. | Yes |
| created_at | Timestamp of receipt creation. | Yes |
| subject | Human-readable subject or file/case description. | Recommended |
| status | Current status, outcome, review level, or next action. | Yes |
| privacy_level | Describes whether the receipt is public, selected-only, redacted, or institution-private. | Yes |
| sharing_mode | Manual export, QR link, public verification page, or permissioned API. | Yes |
| no_auto_sync | Confirms the receipt does not imply database merger or automatic real-time sharing. | Yes for cross-workflow receipts |
| hash | Hash or signature reference for production verification. | Required in production |
| related_receipts | References to other selected receipts cited by this record. | Optional |
{
"protocol": "VRX-1",
"schema_version": "1.0-public-preview",
"receipt_id": "PLENA-HRR-20260510-0001",
"issuer": "PLENA",
"receipt_type": "HUMAN_REVIEW_RECEIPT",
"created_at": "2026-05-10T18:42:00Z",
"subject": "AI-assisted eligibility review",
"status": "Human reviewed · escalated",
"privacy_level": "selected-receipt-only",
"sharing_mode": "manual_export_or_public_link",
"no_auto_sync": true,
"evidence_references": [],
"human_action": {},
"hash": "sha256-or-signature-reference",
"related_receipts": []
}These receipt families extend VRX-1 into the human-to-human service economy while preserving the rule that receipts travel and databases stay home.
Provider, recipient, service category, time/location or remote status, terms agreed, consent, human presence, optional AI-assistance disclosure, attachments, complaint status, and QR verification.
Named human appeared, served, reviewed, explained, approved, rejected, witnessed, refused, or responded.
A named reviewer or issuer declined to certify, verify, seal, or publish, with reason, evidence reviewed, missing evidence, and appeal/resubmission pathway.
{
"protocol": "VRX-1",
"receipt_type": "human_service_receipt",
"provider": "named human or organization",
"recipient": "named recipient or redacted subject",
"service_category": "tutoring | caregiving | coaching | chaplaincy | document_help | repair | interpretation | community_support",
"terms_agreed": true,
"consent_confirmed": true,
"human_presence_confirmed": true,
"ai_assistance_disclosure": "none | drafting | translation | scheduling | triage | summary",
"complaint_status": "none | open | resolved | appealed | refused",
"verification_url": "https://joinplena.com/verify?..."
}Design rule: the receipt is useful without exposing the full underlying file. It says what can be checked, what cannot be checked publicly, and what authority or workflow issued the claim.
The schema should be open enough for others to implement, while PLENA maintains the canonical issuer, reviewer, refusal, revocation, and witness registry.