TenantAtlas/docs/ui-ux-enterprise-audit/target-experience-briefs/customer-review-workspace.md

Customer Review Workspace Target Experience Brief

Metadata

Field	Value
Surface ID	UI-038
Route	/admin/reviews/workspace
Source screenshot	../screenshots/desktop/ui-006-customer-review-workspace.png
Source page report	../page-reports/ui-006-customer-review-workspace.md
Target sidecar	../target-images/target/customer-review-workspace-target.md
Primary persona	Customer reviewer / auditor
Secondary personas	MSP manager, workspace owner, evidence reviewer
Repo-truth posture	Source route and screenshot are repo-verified; target composition is direction only.

Current-State Snapshot

This is the highest customer-safe productization candidate. The report says it must answer what the customer can trust, what changed, which risks are accepted, which evidence supports the state, and what happens next.

Current-State Productization Problems

• Customer-safe language and data exposure need an explicit target.
• Evidence and accepted-risk meaning need first-read clarity without raw diagnostics.
• Review-pack and decision outputs need proof context and shareability boundaries.

Target User Promise

In five seconds, a customer or auditor knows whether the review is ready to trust, what needs attention, and where the evidence can be inspected.

First-Five-Seconds Target

Show review readiness, evidence freshness, accepted-risk summary, management-readable next action, and review pack availability.

Primary Decision

Is this workspace review ready to share, or does it need operator follow-up?

Primary Action

Open review pack.

Secondary Actions

Review accepted risks, inspect evidence, view decision history, request update.

Target Information Hierarchy

1. Customer-safe review posture.
2. Evidence freshness and coverage.
3. Accepted risk summary.
4. Review pack and export readiness.
5. Management-readable next action.
6. Operator diagnostics hidden by default.

Main-View Keep / Promote / Simplify

Treatment	Elements
Keep	Review readiness, evidence basis, accepted risks, review-pack/download concepts.
Promote	Customer-safe summary, evidence freshness, safe share/export state.
Simplify	Internal IDs, raw OperationRuns, provider diagnostics, low-level reason ownership.

Detail Drawer Treatment

Evidence drawer should show customer-readable proof first, operator diagnostics second, and raw/support details only behind explicit capability-gated disclosure.

Advanced/Admin Treatment

Publish, export, regenerate, and diagnostic actions stay behind authorized operator modes, not default customer review.

Hidden/Removed Default Elements

Hide raw JSON, run payloads, provider error details, internal fingerprints, and support-only terminology.

Target Layout Direction

Use a bright/light review-consumption variant and a dark operator companion. The first viewport should read like an audit-ready workspace summary, not an admin list.

Visual Target Direction

Light variant uses ivory surface, graphite text, sand dividers, mint for verified evidence readiness only when backed by proof, amber for attention, and violet for evidence paths. Dark variant preserves the same hierarchy for operator review.

Status/Trust Model

Separate review readiness, evidence freshness, accepted risk, and export/share state. No green success unless proof is verified.

Dangerous Actions

Export, publish, regenerate, or share actions require scope explanation, authorization, audit logging, and customer-safe redaction in later implementation.

Customer-Safe Review Notes

This is customer/auditor-facing. Default copy must be plain language, evidence-backed, and free of raw provider diagnostics or implementation terms.

Workspace/Environment Context

Workspace scope is explicit. Environment-specific evidence summaries must show environment names and must not leak inaccessible tenants.

Empty / Loading / Error States

Empty state should explain that no review pack is ready and offer an operator follow-up path. Loading should show review context. Error state must avoid exposing internal diagnostics to customer mode.

Accessibility Notes

Evidence freshness, accepted risk, and readiness must have text labels. Export/share controls must be clear about file/action scope.

Repo-Truth Classification

Target element	Classification	Notes
Customer review route and screenshot	repo-verified	Spec 323 browser pass reached the route.
Review/evidence/accepted-risk concepts	plausible-existing	Models exist, exact surface mapping needs later spec.
Customer-safe review pack card	foundation-only	Review pack concepts exist but exact export UX needs validation.
Customer mode separation	spec-only	Required target direction, not current runtime proof.
External customer share workflow	conceptual-future-state	Must be separately specified before implementation.

Screenshot-Anchored Image Prompt

Start from ui-006-customer-review-workspace.png. Create a target design direction, not runtime implementation. Preserve customer review consumption. Show review readiness, evidence freshness, accepted-risk summary, review-pack availability, management-readable next action, and hidden diagnostics. Use customer-safe language. Provide dark and light review variants. Avoid generic SaaS dashboards, fake compliance claims, green success without verified evidence, placeholder text, raw OperationRun/provider diagnostics, and runtime implementation claims.

Implementation Pattern Requirements

• Customer-readable decision content first.
• Operator diagnostics second.
• Raw/support evidence third and gated.
• Export/share actions authorized, audited, and redacted.

Later Implementation Candidate

Customer Review Workspace productization.

Non-Goals For Later Implementation

Do not create public customer portals, external sharing, or compliance claims without a separate product/security spec.