TenantAtlas/docs/ui-ux-enterprise-audit/page-reports/ui-006-customer-review-workspace.md
ahmido 0987527d0e feat: customer review acknowledgement lifecycle (343) (#415)
## Summary
- add persisted customer review acknowledgement truth with capability gating and audit emission
- extend the customer review workspace with acknowledgement state, evidence basis details, and accepted-risk lifecycle visibility
- add focused feature and browser coverage plus Spec 343 screenshot artifacts and UI audit updates

## Scope
- Livewire v4 / Filament v5 surface only; no panel provider changes
- no new global assets; no `filament:assets` deployment change for this slice
- includes a PostgreSQL migration for `environment_review_acknowledgements`

## Guardrail / Exception / Smoke Coverage
- reachable UI surface changed: existing `/admin/reviews/workspace` customer-safe page
- UI audit updated in `docs/ui-ux-enterprise-audit/page-reports/ui-006-customer-review-workspace.md`
- screenshot artifacts included under `specs/343-customer-review-attestation-accepted-risk-lifecycle/artifacts/screenshots/`
- spec package includes plan, tasks, repo-truth map, and state contract for the implemented slice

## Notes
- target branch requested: `platform-dev`
- branch pushed from commit `aaaad441fd13dbac54e971ab48765c502ced6b3f`

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #415
2026-06-01 18:00:37 +00:00

49 lines
2.2 KiB
Markdown

# 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, review acknowledgement (attestation) state + action, evidence basis, accepted risk summary, decision summary, review-pack download, and a 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. The acknowledgement action is a write/mutation action and must remain confirmation-gated, capability-gated, and auditable, without legal/e-signature semantics.
## 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. Acknowledgement copy must remain customer-safe and explicitly non-legal (no compliance certification semantics).
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.