# UI-011 Review Register

| Field | Value |
| --- | --- |
| Route | `/admin/reviews` |
| Source | `ReviewRegister` |
| Area / scope | Reviews / workspace |
| Archetype | Reviews |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | `../screenshots/desktop/ui-011-reviews.png` |
| Browser status | Reached through workspace route. |

## First Five Seconds

The page is a review register. It should help an operator understand review readiness, open work, evidence basis, publication state, and customer-facing outputs without requiring detail-page reconstruction.

## Productization Review

- Decision-first: medium.
- Evidence-first: should link to evidence/review packs.
- Context: workspace hub.
- Customer/auditor safety: high because review outputs become customer-facing.
- Diagnostics: review internals should stay below outcome/readiness.

## Information Inventory

Default content should show review subject, lifecycle, readiness, evidence freshness, accepted risk state, and next action.

## Dangerous Actions

Publish, export, review-pack generation, or close actions are high-impact and must preserve auditability and confirmation where applicable.

## Scores

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

## Top Issues

1. Review readiness needs a first-class summary.
2. Customer-safe output state should be obvious.
3. Evidence freshness and accepted-risk visibility need consistent patterns.

## Target Direction

P1 strategic target paired with the Customer Review Workspace target.