# UI-007 Alerts / Alert Deliveries | Field | Value | | --- | --- | | Route | `/admin/alerts` and `/admin/alerts/alert-deliveries` | | Source | `AlertsCluster`, `AlertDeliveryResource` | | Area / scope | Monitoring / workspace | | Archetype | Operations / Monitoring | | Design depth | Strategic Surface | | Repo truth | repo-verified | | Screenshot | `../screenshots/desktop/ui-007-alerts.png` | | Browser status | Opening `/admin/alerts` landed on Alert Deliveries. | ## First Five Seconds The surface currently reads more like a table-backed delivery register than a decision-first alert center. That may be correct for deliveries, but the broader alert center needs a clearer overview/state pattern. ## Productization Review - Decision-first: weak for alert overview, acceptable for delivery history. - Evidence-first: delivery records are explicit. - Context: workspace hub; environment filter should be visible when used. - Customer/auditor safety: not customer-facing by default. - Diagnostics: delivery failure detail should not dominate alert outcome. ## Information Inventory Default content should distinguish alert rules, destinations, deliveries, failures, and required follow-up. Alert delivery rows should show delivery outcome, target, event type, environment attribution, and retry/diagnostic state. ## Dangerous Actions Alert destination enable/disable, destination delete, and test-send actions are high-impact enough to require confirmation/audit review in later specs. ## Scores | IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf | | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | | 3 | 4 | 3 | 3 | 3 | 3 | 4 | 3 | 3 | 4 | 3 | 4 | ## Top Issues 1. `/admin/alerts` needs an explicit alert-center decision model. 2. Delivery table and configuration surfaces should not share the same design priority. 3. Environment filtering should stay clear and chip-backed. ## Target Direction P1 strategic target for Alert Center, domain pattern for deliveries/rules/destinations.