AI content-filter generation tools (suggest-from-history, policy-to-rules) are undocumented

Area: Admin deep-dive (trust/safety) (audit p15a) · Surface: /admin/content-filters/ai/suggest, /admin/content-filters/ai/policy (Admin\ModerationAIController@suggestRules/policyToRules) · Dimension: documentation · Severity: minor

Admins can have the AI propose content-filter rules from recent moderation history, or convert a plain-English policy into concrete filter rules. Neither AI tool is documented in mobieusKnow, even though the AI Community Manager article documents most other AI helpers, so admins won't discover these and the doc set is inconsistent.

Evidence

Admin/ModerationAIController.php:59-80 (suggestRules: reads last 60 mod/report/filter audit actions and asks the model to suggest content-filter rules) and :125-138 (policyToRules: turns a written policy string into content-filter rules). Both are admin-only (requireRole(4)) buttons in the content-filters UI. The Content Moderation article describes filters/filter-groups but not these AI generators: keyword check on /know/content-moderation body shows 'suggest' MISSING, 'policy' MISSING, 'AI suggest' MISSING, 'generate rule' MISSING. The AI Community Manager article (/know/admin-automation-engine) keyword check: 'suggest rule' MISSING, 'policy' MISSING, 'content filter' MISSING. Search `q=AI+rule` -> (none); `q=policy+to+rules` -> (none).

Suggested fix. Document the two content-filter AI generators in the Content Moderation or AI Community Manager article: 'Suggest rules from recent actions' and 'Policy to rules', noting that output is always a draft for admin review before any rule is saved.

Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.