Demo state
Walk the product with seeded case files.
Switch between admissible, ambiguous, and refused examples to preview the Ovrule workspace without running a live classification request.
What Ovrule concluded
This action is acceptable as described. It is narrowly scoped, requested by the affected person, and reduces privacy risk rather than expanding it.
Risk score
- The person affected directly asked for the removal.
- The action reduces exposure of sensitive information.
- The scope is limited to a single clip.
- The team should still preserve internal evidence before removal if policy requires it.
- A takedown should be logged so the moderation record remains auditable.
SAFETY
PASSRemoving the clip reduces plausible privacy and reputational harm rather than creating it.
AUTHORIZATION
PASSThe affected speaker explicitly requested the takedown.
CAUSAL VALIDITY
PASSTaking down the clip plausibly stops further sharing of the accidental disclosure.
REVERSIBILITY
PASSThe platform can restore or review the clip internally if the takedown was mistaken.
IMPACT SCOPE
PASSThe action is narrowly focused on one piece of content and one affected speaker.
CONSENT
PASSThe speaker consented to and requested this class of action.
Case core
Proposed action
Remove a livestream clip after the speaker reports that it reveals accidental medical information.
Affected parties
What the model used, and what it still needs
Speaker removal request
User StatementThe speaker privately reported that the clip includes medical information they did not mean to share.
Clip contents
System StateThe clip remains published and can still be viewed or reposted.
No missing information items were flagged.
No additional evidence gaps were returned.
What got recorded
Decision history
2026-04-22T18:38:11.902Z
Case file created from submitted scenario.
Similar past cases
Related decisions surfaced from the recent receipt register.