# 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.