Ack clock
2 hours
Owner confirms the case is assigned and publishes review ETA.
A rapid content removal flow with receipts, clocks, exceptions, and remedy commitments.
Scenario
Content removals must be fast, but still provide receipts, clocks, and remedy paths.
Jump to
Key sections
Receipt
Every takedown emits a receipt that names the owner and 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" }
}
Clocks
Clocks stay visible even during high-volume enforcement.
2 hours
Owner confirms the case is assigned and publishes review ETA.
24 hours
Human review confirms the removal or restores the content.
72 hours
Restoration, explanation, or alternative remedy is delivered.
Exceptions
Exceptions never erase the receipt or clocks.
Bindings
Use release gates and evidence packs to make this repeatable.
Glossary anchors
This worked example ties back to glossary terms that bind clocks, artifacts, and ownership.