Define the community policy
- Write rules in language members can understand.
- Separate harmful conduct from ordinary disagreement.
- Choose proportionate warning, timeout, kick and ban stages.
- Explain what can be appealed and where.
Build the technical controls
- 01
Secure permissions
Give Stoatmod only the documented capabilities and correct hierarchy.
- 02
Configure categories
Start with the 90% threshold and use observe or review for uncertain areas.
- 03
Add specialised protection
Configure spam, mentions, links, images, join checks and nicknames according to server rules.
- 04
Create a private log channel
Keep review information away from public discussion.
Keep humans in the loop
- Review cases rather than treating automation as unquestionable.
- Verify the real outcome of serious actions.
- Use moderator notes when manual intervention changes the result.
- Give eligible members a private appeal route.
- Review false positives and update the policy.
Measure the right outcomes
Message volume and case totals are context, not a score for community health. Track repeated incidents, moderator workload, successful appeals, retention and whether members understand the rules.