ahmido
8a889a863e
## Summary - add the Spec 323 Tenantial enterprise UI audit foundation package - add the UI/UX audit registry artifacts, templates, and supporting brand context placeholder - update Spec Kit prompts/templates plus PR fast-feedback guardrails for ongoing UI productization coverage ## Scope - docs-first audit foundation only - no runtime Laravel, Filament, Livewire, route, auth, or database behavior changes intended ## Validation - [x] `git diff --check` - [ ] application test suite run ## Notes - primary spec: `specs/323-tenantial-enterprise-ui-audit-foundation/` - this branch also updates `.gitea/pull_request_template.md`, `.gitea/workflows/test-pr-fast-feedback.yml`, and `scripts/check-ui-productization-coverage` to make the coverage gate durable for future UI work Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #383
49 lines
2.1 KiB
Markdown
49 lines
2.1 KiB
Markdown
# 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.
|