Moderation Strike System¶
Domain workflow — instantiates Proportionality Calibration
Implements scaled platform responses for repeated or severe violations, provided it preserves context, appeal, and de-escalation.
A Moderation Strike System is the running machinery that tracks how often an account has offended and steps the platform's response up the scale as the count climbs. Its defining move is temporal accumulation: a single violation carries a strike, strikes add up across time, and each threshold crossed triggers a stronger standing response — from a warning, to reduced reach, to a temporary lock, to permanent removal. Two things keep it a proportionality mechanism rather than a ratchet. First, severe violations can jump strikes, so gravity as well as repetition drives the response. Second, strikes expire: good standing is restored after a clean interval, which is the built-in de-escalation that stops the count from climbing in one direction forever. It is an automated workflow, so its whole discipline is preserving context, appeal, and step-down inside a system built to run at scale without a human in each loop.
Example¶
A large social platform runs a strike system on policy violations like harassment. The workflow is concrete: a confirmed violation adds one strike; strikes decay after ninety days clean. At one strike, the account gets a notice and the post is removed. At two, reach is throttled for a week. At three, a seven-day posting lock. At four within a rolling window, permanent removal. But the system also reads severity: a single credible threat of violence is coded severe and skips straight to the lock, bypassing the count entirely, because repetition is not the point when the first instance is grave. Every automated step ships with a one-click appeal that routes to human review, and every strike carries an expiry date shown to the user. An account that harasses twice, then goes quiet, watches its strikes lapse and its reach restored — the de-escalation path doing exactly what escalation drift would otherwise prevent.
How it works¶
- Assign a strike, weighted by gravity. Each confirmed violation adds to a running count; severe categories add more, or trip a higher response immediately, so the system answers to both recurrence and severity.
- Fire on threshold crossings. Standing response is a function of the current count: named thresholds map to warning, reach limits, temporary lock, and removal, and the jump between them is auditable.
- Expire strikes on clean intervals. Counts decay after a defined violation-free window, automatically stepping standing status back down and restoring lost privileges.
- Wrap every automated action in appeal. Because a machine applies each step, a human-review appeal path is what keeps a miscoded strike from compounding.
Tuning parameters¶
- Threshold spacing — how many strikes separate each response level. Tight spacing punishes fast; loose spacing forgives more before biting.
- Strike decay window — how long a clean run takes to shed a strike. Short windows forgive quickly but may under-deter; long windows retain memory but risk a permanent ratchet.
- Severity multiplier — how much a grave violation counts, up to skipping the ladder entirely. High multipliers protect against slow-drip serious harm but can over-escalate a single miscoded case.
- Rolling window length — the span over which strikes accumulate toward the top rung. Longer windows make removal easier to reach from scattered offenses.
When it helps, and when it misleads¶
Its strength is that it makes recurrence legible and consistent at a scale no human panel could match: the same conduct history yields the same standing response, the response grows only as the record grows, and the expiry path gives even a sanctioned account a visible route back. It is the natural home of the graduated response pattern — escalating consequences tied to a repeated-offense count, with the possibility of stepping back down.[n1]
Its failure mode is that automation makes miscoding compound: a wrongly-assessed strike silently raises the floor for every future case, and a system that can add strikes faster than it expires them becomes the escalation ratchet it was meant to avoid. The classic misuse is gaming and asymmetry — coordinated false reports manufacture strikes against a target while a favored account's strikes quietly never mature. The guarding discipline is a fast, real appeal on every automated step, published expiry dates, and monitoring the strike-issuance distribution for report-brigading — not treating the counter as self-evidently fair because it is numeric.
How it implements the components¶
escalation_threshold— the strike counts that trigger each stronger response are literal, auditable escalation thresholds tied to recurrence and gravity.de_escalation_path— strike expiry after a clean interval is the built-in step-down that restores standing and privileges automatically.response_scale— the ordered rungs from notice through reach-limit, lock, and removal are the platform's response scale, including the restoration rung.severity_assessment— coding violations by gravity, and letting severe ones skip the count, is a severity read layered onto the recurrence engine.
It weighs no broad burden_assessment on bystanders or the wider audience and maps no affected_interest_map — the Risk-Based Enforcement Protocol does that — and it keeps no consistency ledger against precedent (precedent_comparator); that lookup discipline is the Sanction Matrix.
Related¶
- Instantiates: Proportionality Calibration — it is the graduated-response variant running as always-on platform machinery.
- Consumes: Sanction Matrix can supply the standing response assigned at each strike level.
- Sibling mechanisms: After-Action Proportionality Review · Disciplinary Guideline · Proportional Remedy Menu · Response Matrix · Risk-Based Enforcement Protocol · Sanction Matrix · Least-Restrictive Alternative Screen
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Moderation Strike System operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it implements scaled platform responses for repeated or severe violations, provided it preserves context, appeal, and de-escalation.
Independent corroboration: The frozen evidence defines Moderation Strike System as 'Implements scaled platform responses for repeated or severe violations, provided it preserves context, appeal, and de-escalation', so its operative form is Control, Automation & Runtime.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Historically ambiguous
Present-day reach: Multi-domain
Rationale: Escalating sanctions for repeated or severe violations descend from legal proportionality and graduated enforcement.
Related originating lineages:
- Communication & Media Studies — Platform moderation and copyright enforcement developed the familiar digital strike-system form.
- Organizational & Management Science — Progressive discipline provides a parallel institutional practice.
- Ethics of Technology & AI Governance — Responsible governance materially contributes expiry, appeal, and de-escalation safeguards.
Review resolution: Both independent reviews agree on primary origin law_governance; reconciliation resolves secondary fields (reported_ambiguity, alternate_origin_disagreement, origin_mode_disagreement, domain_reach_disagreement). Alternate origins retained (organizational_management, tech_ethics_ai_governance, communication_media_studies) are the union of reviewer-supported formative lineages with explicit rationales, not a list of later application domains. Present-day breadth is represented separately as domain_reach=multi_domain; origin_mode=historically_ambiguous records the historical relationship among lineages. Confidence is conservatively reconciled to medium, and encyclopedia_synthesis=false preserves either reviewer's finding that the encyclopedia generalized the mechanism.
Attribution caveat: The mechanism has converging legal-regulatory and platform-practice lineages.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Graduated response is an enforcement pattern in which consequences escalate with each repeated or worsening offense — used in settings from copyright "three-strikes" schemes to platform moderation — and which counts as proportionality only when escalation thresholds are visible and a de-escalation or expiry path exists. ↩