SUMMARY: A moderation receipt records the action taken on a user, comment, room, or thread and the reason that action was taken.
Moderation becomes stronger when it leaves a clear operational trail. A receipt does not need to expose private details. It should identify the surface reviewed, the rule or pattern involved, the action taken, and any follow-up watch item.
The receipt protects the community from arbitrary decisions and protects the operator from forgetting why a decision was made.
Receipt Fields
Surface: comment queue, forum topic, chat room, user account, post, or public endpoint.
Pattern: spam link, repeated status flood, suspicious registration, off-topic post, stale route, or access anomaly.
Action: approve, delete, hold, watch, summarize, restrict, or escalate.
Remainder: what still needs review after the immediate action is complete.
Use Case
Use moderation receipts with route receipts. Route receipts prove a path was checked. Moderation receipts prove a human-facing surface was handled with care.
Operator Rule
If an action changes what members can see, leave enough receipt for the next review to understand the change.
Field assessment: transparent moderation is a maintenance practice, not a performance.