Problem: AbuseFilters are a great way of preventing problematic edits before they happen. However, guessing "problematic" is currently done using user segmentation, common phrases used by vandals etc. We have a much better tool to determine if an edit is destructive: ORES. If we were able to prevent all edits above a certain threshold, the workload on patrollers would be significantly reduced and, possibly, would prevent some communities from requesting and all-out IP-editing ban.
Proposed solution: Expose the raw ORES "damaging" score as a variable in AbuseFilter
Who would benefit: Patrollers and admins would have less work
More comments: Exposing ORES levels from the Special:RecentChanges interface (very likely, likely, less likely, unlikely) would also be OK.
