feat: expand SHD.build community platform branding

docs/DESIGN_SYSTEM.md

@@ -1,6 +1,10 @@
 # SHD.build Design System
 
-This document defines the visual language for SHD.build. New pages should feel like part of the same tactical data network as the admin dashboard, while public pages may use more space and larger editorial typography.
+This document defines the visual language for SHD.build, the independent
+Division Resurgence community for builds, guides, game data, news, and
+discussion. New pages should feel like part of the same tactical intelligence
+network as the admin dashboard, while public pages may use more space and larger
+editorial typography.
 
 ## Design principles
 
@@ -64,8 +68,32 @@ widths and becomes a two-column touch-friendly grid on narrow mobile screens.
 
 The footer repeats the complete SHD brand lockup used by the global header:
 double-ring SHD mark, white `SHD`, orange `.build`, and the restrained
-`LOADOUT NETWORK` descriptor. Do not substitute a plain text wordmark or color
-the complete product name orange.
+`RESURGENCE COMMUNITY` descriptor. Do not substitute a plain text wordmark or
+color the complete product name orange.
+
+### Community platform positioning
+
+SHD.build is a full Division Resurgence community, not solely a loadout tool.
+Primary product language and global navigation must represent five durable
+channels: News, Database, Builds, Guides, and Builder. Loadout-specific terms
+remain appropriate inside build routes, but the global brand descriptor,
+homepage metadata, hero, sign-in introduction, and footer describe the broader
+community platform.
+
+The homepage uses a community-channel grid to establish this information
+architecture. Each channel has an operational code, plain-language purpose,
+and explicit destination. New channels should extend this reusable pattern
+rather than turning the navigation into an undifferentiated list. Honest
+launch-state pages may describe planned capability, but must distinguish queued
+features from live data. Database landing metrics use approved active records,
+not invented activity counts.
+
+On desktop the five public destinations remain visible in the global
+navigation. Mobile navigation numbers destinations dynamically so adding a
+channel cannot collide with Inbox, Profile, or ISAC codes. Community channel
+cards collapse from four columns to two and then one; hover color alone never
+replaces their textual destination labels, focus-visible treatment, or pressed
+feedback.
 
 Contact notifications use the mandatory ISAC visual identity because they are
 operational inbound messages. The notification carries a concise preview and a