## 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
1.8 KiB
Markdown
49 lines
1.8 KiB
Markdown
# UI-008 Audit Log
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Route | `/admin/audit-log` |
|
|
| Source | `AuditLog` page |
|
|
| Area / scope | Evidence / audit / workspace |
|
|
| Archetype | Evidence / Audit |
|
|
| Design depth | Strategic Surface |
|
|
| Repo truth | repo-verified |
|
|
| Screenshot | `../screenshots/desktop/ui-008-audit-log.png` |
|
|
| Browser status | Reached through workspace route. |
|
|
|
|
## First Five Seconds
|
|
|
|
The page is clearly an audit log. Its product role should be audit evidence first, diagnostics second, with explicit filters and no raw payload dominance in the default layout.
|
|
|
|
## Productization Review
|
|
|
|
- Decision-first: medium, because audit is investigative.
|
|
- Evidence-first: strong.
|
|
- Context: workspace hub with optional environment filter.
|
|
- Customer/auditor safety: high for export/review contexts.
|
|
- Diagnostics: raw metadata should be deliberately disclosed.
|
|
|
|
## Information Inventory
|
|
|
|
Default content should expose action, actor, target, workspace/environment attribution, timestamp, and outcome. Event inspection should stay scoped by filter and entitlement.
|
|
|
|
## Dangerous Actions
|
|
|
|
No visible destructive action should be primary. Export or detail-inspection actions require tenant-safe data exposure review.
|
|
|
|
## Scores
|
|
|
|
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|
|
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
|
|
| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 3 | 3 | 4 | 4 | 4 |
|
|
|
|
## Top Issues
|
|
|
|
1. Selected-event detail must respect active environment filters.
|
|
2. Customer/auditor export language needs dedicated review.
|
|
3. Metadata/raw payload hierarchy should stay secondary.
|
|
|
|
## Target Direction
|
|
|
|
P1 strategic target as the auditability proof pattern for workspace and environment-attributed events.
|