Record the deadline, the action, and the consequence if it is missed.

What a Deadline Receipt is

A Deadline Receipt is an organised record of a date-bound obligation. It records:

• The subject (what the deadline applies to), the date and time, and the responsible party.
• The required action, the consequence of missing the deadline, and the correction or extension path if one exists.
• Optional pre-deadline reminder dates, an optional link to the originating submission, and an optional supersedes pointer if the deadline has been extended or amended.

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 receipt creator that, on the stated date, the listed deadline applied to the named subject with the listed consequence.

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 deadline is enforceable by law, regulation, or any external authority. The receipt records what the issuer attests; the issuer’s authority to set the deadline 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 date-bound obligations, consequences, and remedies. A Deadline Receipt is an organised record of a deadline and the action it requires, 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 automated pre-deadline reminders delivered by the responsible party’s chosen channel. These remain roadmap items.