A Human Review Receipt records that a named human reviewer considered specific evidence and reached a decision — accept, refuse, escalate, or correct — with the reason recorded and an appeal or correction path stated. The receipt is self-attested by its creator; its content is tamper-evident via SHA-256.
A structured record that a named human reviewer considered a specific case, decision, AI output, document, claim, or service event at a recorded moment, and reached a decision. It captures the reviewer (name or role), the review scope, the date and time, the evidence considered, the decision made, the reason for accept / refuse / escalate / correct, the appeal or correction path, and whether AI assistance was used during the review.
It is the institutional moat receipt for AGI-era accountability: the artefact that says a human was in the loop, here is who, here is what they saw, and here is what they decided.
PlenaProof does not certify AI systems or guarantee regulatory compliance. PlenaProof helps institutions document review, accountability, and decision trails. A Human Review Receipt is an organised record of a review event, formatted so a student, client, regulator, board, funder, court, employee, journalist, parent, donor, partner, or public agency can read it. It is not a certificate, not a court filing, not a regulator-issued audit, and not an official acknowledgement by any external authority.
Future production releases may add issuer signing keys, external timestamp anchoring, a public revocation registry, and certified-reviewer status. These remain roadmap items.
Human Review Receipt v1 inherits the established VRX-1 schema conventions. All keys are alphabetised before hashing; the hash field is computed over the canonical JSON with the hash field itself removed. The published schema file is vrx1-human-review-receipt.schema.json.
All processing happens in your browser. Nothing is sent to a server. The receipt JSON, hash, and verification URL are produced locally and can be exported, printed, or saved to the local Wallet preview.
Paste a receipt JSON or upload a .json file. The page recomputes the SHA-256 over the canonical JSON (with the hash field removed) and compares it to the hash stored inside the receipt. A match means the receipt content has not been modified since the hash was computed; it does not mean the facts in the receipt are true, that the reviewer was independent, or that any external authority must accept the receipt.
Receipts you save to the local Wallet preview are stored only on this browser, across all VRX-1 receipt-type pages. They are not synced and not uploaded. Clearing browser data on this device removes them.
A Human Review Receipt sits at the centre of the AI Accountability & Human Review suite and connects to related receipt types and platform workflows.
The institutional suite this receipt anchors. Helps institutions document when AI was used, who reviewed the output, what was accepted or rejected, what was escalated, and what audit trail was produced. Output: Human Review & AI Decision Audit Pack.
The platform whose diagnostic logic anchors the AI Accountability suite. Pairs with Human Review Receipts when a decision is challenged on fairness, bias, or appeal-rights grounds.
The sibling AGI-era moat receipt. When a Human Review Receipt records a refuse decision, a Refusal Receipt can document the refusal with reason codes and a correction path.
When a review is later questioned by a regulator, board, court, journalist, or public agency, PROVA helps organise the challenge-ready evidence packet around the review record.
Preserves review records across staff turnover, leadership change, and time, so a decision made today can still be reviewed five or twenty years from now.
When the review concerns AI-generated content, DETECTA's diagnostic logic supports the review with risk signals appropriate to the suite's truth boundary.
For reviews that involve AI-use policies, notices, or consent language, LEGIBLA helps make the policy and notice content readable to the reviewed party.
Saved receipts appear in the Wallet's local lifetime timeline preview. Stored on this device only.
The entry-point receipt. Many Human Review Receipts trace back to an earlier submission; the optional linked_submission_receipt_id field carries the cross-reference.
The shared schema conventions, field meanings, and integrity-note pattern that this receipt type inherits.