Add automated ISAC system notifications

docs/DESIGN_SYSTEM.md

@@ -129,6 +129,21 @@ daily delivery targets 10:00 AM in `America/New_York` so the Eastern wall-clock
 time remains stable across daylight-saving transitions. On mobile, cadence
 segments wrap to two columns and each review category becomes its own row.
 
+ISAC System Configuration is a distinct navigation domain from System
+Oversight. It contains operational configuration such as Automated Messages and
+read-only observability such as System Metrics. Automated-message editors use
+the standard horizontal edit lifecycle: successful edits close the editor,
+validation preserves it, and event triggers remain explicit. Content, enabled
+state, post-event delay, primary destination, and up to eight action callouts
+are displayed as structured fields rather than raw JSON.
+
+Automated ISAC messages may expose multiple square action callouts in the
+notification inbox and detail view. Callouts wrap on desktop and become
+full-width touch targets on mobile. Each retains a specific verb and
+destination; do not replace the set with a generic “open” action. External
+community actions such as Discord use secure HTTPS destinations while internal
+actions use routed paths.
+
 Contact notifications use the mandatory ISAC visual identity because they are
 operational inbound messages. The notification carries a concise preview and a
 specific action to an authorization-checked full record. Full messages never