Pretend you are the community mod so soft enforcement rules and heroic volunteer hours fail before the guidelines change becomes public policy.
Optimistic guideline rewrites optimize for the principle that looks clean on a blog post. The community-mod seat does the opposite. It asks which edge cases still lack a playbook, which bans create appeal storms you cannot staff, which volunteer mods will quit under the new load, and which creators will read the change as a loyalty test. A polished values page is not evidence that moderators can apply the rule at 2 a.m. without inventing policy.
This is one of the core moves in a community guidelines war game: after you describe the trust upside, seat a careful moderator and make them try to decline. The output you want is not cheerleading. It is a short list of material objections, the exhibits each needs, and the edits that would survive them.
How to cast the seat
Name a real mandate: enforce the new line without inventing staff mid-week, protect power users without carving silent exceptions, or underwrite a crackdown without pretending appeals are free. Give constraints: tooling you will not ship this month, volunteer hours you will not pretend away, and residual risk you will not accept. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear.
Write the seat into the prompt as a named role with a mandate. Example: "Community mod: list the top reasons to pause or sequence this guidelines change, the assumption with the weakest source, the enforcement or appeal gap that worries you most, and the ten diligence questions you would send after the meeting. Stay inside a realistic mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons to delay, sequence, or narrow the rule.
- The assumption that looks strongest and is least sourced.
- The edge case, appeal path, or staffing mismatch that would worry you most.
- What would make you approve instead.
- The ten hardest diligence questions you would send in writing.
Run that brief in Pingpong against the real draft, recent incident notes, and mod roster. Follow with a home-team response pass so you leave with edits and named owners, not only fear. When the decision sits near a trust and safety hire or a terms update, run this seat after legal and support attacks so it can use earlier objections as ammunition.
When the change leans on one volunteer lead, one opaque ban tool, or one "we will clarify later" clause, force the seat to price concentration risk in writing. Ask what happens if that person is out, if the tool false-positives, or if two mods apply the rule differently. Concentration that only appears in an appendix still counts. Pair with war-game a community guidelines change, stress-test a terms of service update, pretend you are the support agent, war-game a customer escalation, and the war-game decisions hub. See how to run a Pingpong.