ahmido 3eff4d8579 Spec 325: add screenshot-anchored strategic target images (#385 )

## Summary
- add the Spec 325 artifacts for screenshot-anchored strategic target images
- update the UI/UX enterprise audit documents to capture strategic surfaces and grouped follow-up candidates
- add supporting follow-up specs, target experience briefs, and target image assets for the audit workflow

## Testing
- not run (documentation/spec artifact changes only)

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #385

2026-05-18 07:18:13 +00:00

2.2 KiB

Raw Blame History

Customer Review Workspace Target Image Sidecar

Not Implementation Truth

This target image is visual direction only. It is not runtime implementation truth, not a product capability claim, and not a substitute for later repo, RBAC, data, audit, and browser verification.

Links

Item	Link
Source 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 brief	`../../target-experience-briefs/customer-review-workspace.md`
Dark target image	`customer-review-workspace-target-dark.png`
Light target image	`customer-review-workspace-target-light.png`

Transformation Table

Current state	Target direction
Customer review value is present but needs final hierarchy.	Review readiness, evidence freshness, and accepted risk become first-read.
Raw/internal diagnostics could leak into review framing.	Customer-safe content is default; diagnostics are hidden.
Review pack context needs proof language.	Review pack availability is tied to evidence and share scope.

Repo-Truth Classification

Element in target image	Classification	Implementation note
Review workspace route	repo-verified	Existing route/screenshot anchor.
Review/evidence/accepted-risk concepts	plausible-existing	Existing product areas, exact links need verification.
Customer-safe review pack card	foundation-only	Requires export/share behavior verification.
Customer mode split	spec-only	Target direction, not runtime proof.
External sharing	conceptual-future-state	Separate spec required.

Conceptual Elements Requiring Verification

Review readiness derivation
Evidence freshness source
Accepted-risk summary source
Export/share authorization and audit

Implementation Notes

Later implementation should separate customer-readable content, operator diagnostics, and support/raw evidence.

Do Not Implement Blindly

Do not expose raw OperationRuns, provider diagnostics, fingerprints, or internal reason ownership in customer-facing default views.

2.2 KiB Raw Blame History