Toxicity, account-age, and brigading controls for automated moderation — with a signed reason for every removal.
For: Trust & safety and community ops running automated moderation
Removes content above the toxicity threshold for young accounts.
Escalates removals on established accounts for human review.
Restrains mass actions that match a coordinated-brigade pattern.
# Reddit Moderation Safety Baseline
# Fork: adjust thresholds; every removal emits an appeal-ready dossier.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: reddit-mod-safety-baseline
surface: reddit
standards: [auditable-enforcement]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: toxicity_threshold
when: "action == 'moderation.remove'"
decision: |
REMOVE IF toxicity > 0.85 AND author.account_age_days < 30
ESCALATE IF toxicity > 0.85
ALLOW OTHERWISE
reason_code: toxicity_over_threshold
- name: account_age_guard
when: "action == 'moderation.remove'"
decision: |
ESCALATE IF author.account_age_days >= 365
ALLOW OTHERWISE
reason_code: established_account_review
- name: brigading_signal
when: "action == 'moderation.bulk_remove'"
decision: |
RESTRAIN IF signals.coordinated_pattern == true
ALLOW OTHERWISE
reason_code: coordinated_brigade_suspected
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
Follow the install path for this surface, then paste the forked YAML as your policy config.
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.