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 Permalink Blame History

Restore Safety Workflow 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/workspaces/{workspace}/environments/{environment}/restore-runs` plus create/view family
Source screenshot	`../../screenshots/desktop/ui-014-restore-runs.png`
Source page report	`../../page-reports/ui-014-restore-runs.md`
Target brief	`../../target-experience-briefs/restore-safety-workflow.md`
Dark target image	`restore-safety-workflow-target-dark.png`
Light target image	`restore-safety-workflow-target-light.png`

Transformation Table

Current state	Target direction
Browser review was blocked by capability/state.	Target is explicitly marked as safety direction, not current UI proof.
Restore could look like normal create/list UI.	Restore appears as a high-friction safety workflow.
Preview/result/evidence truth needs separation.	Safety gates, preview, confirmation, operation, and evidence are distinct.

Repo-Truth Classification

Element in target image	Classification	Implementation note
Restore route family	repo-verified	Route exists, fixture blocked.
RestoreRun and OperationRun concepts	repo-verified	Existing models.
Safety gate stepper	foundation-only	Product safety requirement, exact runtime steps need spec.
Hard confirmation copy	spec-only	Target wording only.
Partial restore conflict model	conceptual-future-state	Needs separate verification.

Conceptual Elements Requiring Verification

Actual dry-run/preview data shape
Validation gate sequence
Hard confirmation text and rules
OperationRun and evidence result links

Implementation Notes

Later implementation must enforce preview, explicit confirmation, authorization, audit, OperationRun continuity, and post-run evidence.

Do Not Implement Blindly

Do not implement restore provider writes or confirmation behavior from a visual artifact without the restore safety spec and tests.

2.2 KiB Raw Permalink Blame History