You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: design: moderation preset tiers — legible policy presets that compile to concrete rules #6007
Part of the worlds design program: #5955. Wave-2 follow-up from the prior-art research (Lane B item 26); parent topic issue: #5973. Research source: workspace/scratch/worlds-capabilities-brief-2026-11-04/prior-art-research.md.
Precedent
What made third-party moderation bots adoptable was not rule power but legibility: Paladin maps a content rating (G/PG/PG-13/R) to preset AutoMod configurations and re-syncs them; admins choose a tier, not a rule list (https://www.shapedimage.com/paladin-docs.html). No major platform offers first-party cross-community rule-pack subscription with versioning — id would be building ahead of the field, which argues for keeping presets few and dead simple.
Nothing landed: no preset tier table exists in the issue's references yet — the Paladin precedent is cited as research input, not as an existing id artifact. This is design work to do, not a duplicate.
Scope discipline is right as filed: presets compile to concrete rules and remain adjustable (starting point, not a lock); the field has no first-party cross-community rule-pack subscription, so few-and-simple is the stated design constraint.
Ordering recorded:#6007's tier table sets concrete values (filter strictness, report→quarantine thresholds, pre-approval) that are parameters of the moderation library designed in #5973 and expressed in its pack format — so #5973's interface/parameter model lands first (or the tier table is written explicitly against its draft parameter names). It also inherits #5973's dependency on the #5958 capability model for what a moderation library may do.
No follow-up task enqueued — this issue is itself the work item, already in the queue system. Task 10373 completes as triaged.
Activity
developing-today commentedon Nov 5, 2026
CODE-1673
dezren39 commentedon Nov 5, 2026
Triage — task 10373 (lane code-s)
Verdict: live design issue, small and correctly scoped; child of #5973. Stays OPEN.
Evidence checked fresh 2026-11-05:
Ordering recorded: #6007's tier table sets concrete values (filter strictness, report→quarantine thresholds, pre-approval) that are parameters of the moderation library designed in #5973 and expressed in its pack format — so #5973's interface/parameter model lands first (or the tier table is written explicitly against its draft parameter names). It also inherits #5973's dependency on the #5958 capability model for what a moderation library may do.
No follow-up task enqueued — this issue is itself the work item, already in the queue system. Task 10373 completes as
triaged.