feat: add automated community moderation

docs/architecture.md

@@ -82,6 +82,24 @@ explains registration closure. This guard runs on the server, so a crafted form
 submission or OAuth callback cannot create an account while registration is
 closed.
 
+## Community content moderation
+
+Comments, profile biographies, custom avatars, guides, and build descriptions
+share the moderation lifecycle documented in
+[`CONTENT_MODERATION.md`](CONTENT_MODERATION.md). Local rules and the configured
+provider classify each submission before publication. Clean submissions can
+publish without human work. Flagged submissions and fail-closed provider errors
+enter the appropriate Oversight queue.
+
+Agents may report visible content they do not own. Reports enter Oversight
+without hiding the content. Human decisions require a reason and append an
+audit event. Long-form edits that need review use immutable pending revisions
+so the last approved biography, guide, or description remains public.
+
+ISAC Site Controls owns provider behavior, content scopes, thresholds, link and
+PII checks, and allowed or banned terms. API credentials remain in server
+environment configuration.
+
 ## Increment plan
 
 1. Product shell and anonymous local-draft builder.