Harm receipt format

Specifies what the system owes a user when it is wrong: acknowledgement, explanation, remedy path, and time bounds.

Silence is not an acceptable resolution state.

What this enforces

• Repair obligations are explicit.
• Users receive a bounded remedy path.
• The burden of proof is limited.

How to use

1. Issue a harm receipt whenever a material error is discovered.
2. Include remedy path, time bounds, and escalation contact.
3. Log harm receipts as governance events, not support tickets.

Download template

If a field is hard to fill, that is the governance gap this artifact exposes.