Worked example

Content moderation takedown

A rapid content takedown that issues a receipt, runs 2-, 24-, and 72-hour clocks, bounds its exceptions, and restores content when overturned.

Receipt issued at removal time

Every takedown issues a receipt that names the owner and the appeal path.

{
  "schema_version": "1.0.0",
  "receipt_id": "RCP-2026-1188",
  "issued_at": "2026-05-21T09:44:10Z",
  "owner": { "name": "Trust & Safety", "role": "System owner" },
  "subject": { "id": "post-88014", "type": "content" },
  "action": { "class": "PUBLISH", "description": "Remove content", "reversible": true },
  "decision": { "decision_type": "takedown", "reason_codes": ["HARASSMENT", "POLICY-3.2"] },
  "clocks": { "ack": { "hours": 2 }, "review": { "hours": 24 }, "remedy": { "hours": 72 } },
  "appeal_path": { "url": "/appeals/content", "channel": "in-app form" }
}

Acknowledgment, review, and remedy clocks

The clocks stay visible when enforcement volume spikes.

The clocks, drawn to one scale

Each bar runs from the decision to its deadline, on one scale of hours.

Hour 0 The content is removed and a receipt is issued.

  1. Acknowledge 2 hours
    Due
    Trust & Safety confirms who has the case and tells the poster when review will finish.
    If missed
    The case goes to a senior reviewer.
  2. Review 24 hours
    Due
    A person keeps the content down or restores it.
    If missed
    The content is restored by default, unless a logged safety escalation holds it.
  3. Remedy 72 hours (3 days)
    Due
    The poster gets the content restored, an explanation, or another remedy.
    If missed
    The breach is logged against Trust & Safety.

Bounded exceptions for safety or legal holds

Exceptions never erase the receipt or clocks.

  • A safety escalation can delay restoration. The review must still finish on its clock.
  • A legal hold can keep the content hidden for a time. The appeal stays open.
  • Exceptions are logged in the Exceptions register.

Remedy

Restore, explain, or compensate

The creator or user whose content was removed can see the remedy path.

  • If the takedown is overturned, the content is restored.
  • If it is upheld, the poster gets the reason and the evidence it rested on.
  • If the removal cuts off the poster's income or access, the appeal is reviewed first.
  • Each takedown overturned after a challenge is counted against the policy rule it cited, here POLICY-3.2. The count goes to Trust & Safety, which owns the rule and the filter that applies it. When the count passes a set number, it reviews both and records what changed.

Where this fits

Platform enforcement

Whether a person's post stays up, their account stays open, or their listing stays visible.

Scored cases
No platform case has been scored yet.
Standards to adopt
Run first
Corrective capacity self-assessment. Ask whether an upheld challenge changes the filter or only restores one post.

Release gates and evidence packs make every takedown run the same way. Each release attaches its receipts to its pack, and each receipt maps to the packs for STD-01 and STD-02.

Terms used: Time transparency Stable clock Bounded duration Decision artifact Traceable ownership Safe pause Time to restore (TTR) Time to halt (TTH) Appeal passage rate

The full entry, and where the framework does less →