# UI-006 Customer Review Workspace

| Field | Value |
| --- | --- |
| Route | `/admin/reviews/workspace` |
| Source | `CustomerReviewWorkspace` |
| Area / scope | Customer review / workspace |
| Archetype | Customer Workspace |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | `../screenshots/desktop/ui-006-customer-review-workspace.png` |
| Browser status | Reached through local workspace route. |

## First Five Seconds

This is the most important customer-safe productization candidate. The page should answer what the customer can trust, what changed, what risks are accepted, which evidence supports the state, and what should happen next.

## Productization Review

- Decision-first: strong candidate, needs final target hierarchy.
- Evidence-first: must anchor all claims to review/evidence artifacts.
- Context: workspace-level customer view.
- Customer/auditor safety: primary concern.
- Diagnostics: raw/internal details must stay hidden by default.

## Information Inventory

Default content should include review readiness, evidence basis, accepted risk summary, decision summary, review-pack download, and management-readable next action.

## Dangerous Actions

Customer-facing surface should be read-first. Export/download and publish/review actions need clear scope, audit, and language.

## Scores

| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
| 3 | 3 | 3 | 5 | 3 | 3 | 4 | 3 | 3 | 4 | 3 | 4 |

## Top Issues

1. Needs customer-safe language and data exposure review before sellable use.
2. Evidence and accepted-risk meaning should be visible without raw diagnostics.
3. Requires individual target mockup, not only cleanup.

## Target Direction

P0 individual target mockup and follow-up implementation wave. This page is a core sellability surface.