VRX-1 · Receipt Type 6 · Correction-Trail · d19.82 Reference

Amend a receipt without erasing what came before.

A Correction-Trail Receipt is what an institution or individual issues when a prior receipt needs to be amended, withdrawn, sharpened, or superseded. It points back at the receipt being corrected, records the corrector, the kind and substance of the change, the reason, and the date. Originals are not rewritten; corrections travel alongside them. The receipt is self-attested by its creator; its content is tamper-evident via SHA-256.

What a Correction-Trail Receipt is

A Correction-Trail Receipt is an organised record of an amendment to a prior receipt. It records:

  • Which receipt is being corrected (by ID and type), who is doing the correcting, when, and the position of this correction in the chain (correction_index).
  • The kind of correction (factual error, typo, missing information added, superseded by review, withdrawn, clarification), the substance of the change, and the reason.
  • An optional supersedes pointer to the immediately prior Correction-Trail Receipt in the chain when this is the second or later correction; and an optional Human Review Receipt ID when a review authorised the correction.

What this receipt proves

  • The receipt content has not been altered since the hash was computed — anyone holding the JSON can recompute the SHA-256 and confirm a match.
  • A creation timestamp recorded by the device that built the receipt.
  • A self-attestation by the corrector that, on the stated date, the named prior receipt was amended in the stated way for the stated reason.

What this receipt does not prove

  • That the facts inside the receipt are true. The receipt is self-attested by its creator.
  • That the receipt is signed by an institutional issuer. The current reference implementation uses no signing key.
  • That the timestamp is anchored to an external clock or registry. The timestamp is taken from the device that built the receipt.
  • That the original receipt was wrong. The Correction-Trail Receipt records that the corrector judged a change was needed; the original is preserved unchanged for inspection.
  • That any institution, regulator, court, employer, university, board, or platform must accept the receipt as evidence. Acceptance is decided by the receiving party.

Truth-boundary preserved

PlenaProof does not certify AI systems or guarantee regulatory compliance. PlenaProof helps institutions and individuals document amendments, sharpenings, withdrawals, and the audit trail across them. A Correction-Trail Receipt is an organised record of an amendment to a prior receipt, traced back to the receipt it amends, 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 issuer-signed correction chains and external timestamp anchoring of the correction events. These remain roadmap items.

Schema preview

Show schema preview (technical)

Correction-Trail 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-correction-trail-receipt.schema.json.


  

Build a Correction-Trail Receipt on this device

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.

The receipt_id of the receipt whose content this correction amends.
1 = this is the first correction in the chain; 2 = second correction; and so on.
When correction_index = 1 this is normally blank (the chain starts here, pointing back at the original receipt via "Corrected receipt ID" above). When correction_index ≥ 2 this should point at the prior Correction-Trail Receipt in the chain.
If a Human Review Receipt authorised the correction.
What this build produces. A Correction-Trail Receipt in JSON, with a SHA-256 hash over its canonical form. The receipt is self-attested; PlenaProof does not sign it, anchor it externally, or certify its claims. Cryptographic signing, issuer-key validation, revocation registry, external timestamp anchoring, and backend audit logging remain future production work.

Verify a receipt

Paste a receipt JSON below (or upload one) to recompute its SHA-256 over the canonical JSON (with the hash field removed) and compare with the embedded value. The receipt does not need to have been created on this device.

Saved to this device

All VRX-1 reference pages share the same on-device wallet preview. Saved receipts are stored in your browser's local storage and are not sent to any server. Clearing your browser data will remove them.

Connected PlenaProof surfaces

A Correction-Trail Receipt is the audit-trail companion to every other receipt type. It connects to the receipt being corrected and to the platforms that anchor durable record-keeping.

Institutional Continuity Suite →

The suite where amendments and corrections to past records most need a durable trail. The Correction-Trail Receipt makes the change explicit and reviewable across staff turnover, leadership change, and time.

AI Accountability & Human Review Suite →

When a Human Review Receipt is amended after later evidence surfaces, the Correction-Trail Receipt is the canonical record of the change. Pairs with Human Review Receipt via the linked_human_review_receipt_id field.

VRX-1 Submission Receipt →

Submission Receipts are corrected when the intake record itself was inaccurate (wrong date, misspelled submitter name, missing service reference).

VRX-1 Human Review Receipt →

Human Review Receipts are corrected when a later review supersedes or revises the original decision, when the decision reason needs to be sharpened, or when AI-assistance was misreported.

VRX-1 Refusal Receipt →

Refusal Receipts are corrected when the missing items list is amended, when an appeal succeeds, or when the refusal is withdrawn after additional evidence is provided.

VRX-1 Missing-Item Receipt →

Missing-Item Receipts are corrected when items are added to the list, removed from it, or when the required-by window is amended.

VRX-1 Deadline Receipt →

Deadline Receipts are corrected when an extension is granted, when the deadline is brought forward, or when the deadline is withdrawn.

CONSERVA — Life Proof Archive →

CONSERVA's individual-side role anchors the durable preservation of corrections alongside the records they correct: the original is not deleted, the correction is added, and both travel together through the archive.

PROVA — Personal Evidence & Dispute Packet →

When the corrected receipt is itself part of an appeal or dispute, the Correction-Trail Receipt becomes part of the Personal Evidence Readiness Packet showing that the institution made a documented amendment.

Receipt Redaction & Correction Policy →

The PLENA policy page explaining the doctrine: corrections amend rather than erase; both the original and the correction travel together; neither is silently rewritten.

PlenaProof Vault — Life Proof Archive →

Saved receipts appear in the Wallet's local lifetime timeline preview. Stored on this device only.

VRX-1 Schema reference →

The consolidated reference page for all six gating receipt schemas, including this one.