List what is missing, why it’s needed, and how to provide it.

What a Missing-Item Receipt is

A Missing-Item Receipt is an organised record returned to a submitter when their application, form, claim, or document set is incomplete. It records:

• What was submitted (the submission context) and when it was received.
• The specific items that are missing, the consequence of not providing them, and the correction path the submitter must follow.
• A required-by date where one applies, and an optional escalation route if the submitter believes the request is incorrect or cannot be met.

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 recipient institution or role that, on the stated date, the listed items were considered missing from the named submission.

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 items listed are required by law, regulation, or any external authority. The receipt records what the institution has asked for; the institution’s authority to ask is decided elsewhere.
• 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 intake, completeness checks, and the correction trail that follows. A Missing-Item Receipt is an organised record of an incompleteness finding and the correction path it triggers, 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-attested completeness criteria pulled from a published submission schema. These remain roadmap items.