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

Environment Dashboard 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}`
Source screenshot	`../../screenshots/desktop/ui-002-environment-dashboard.png`
Source page report	`../../page-reports/ui-002-environment-dashboard.md`
Target brief	`../../target-experience-briefs/environment-dashboard.md`
Dark target image	`environment-dashboard-target-dark.png`
Light target image	`environment-dashboard-target-light.png`

Transformation Table

Current state	Target direction
Backup, recovery, verification, and operations have similar weight.	Readiness posture and blocker reason become the first read.
Dangerous downstream actions are implied by domain links.	Mutation scope and safety context are called out before action.
Proof and diagnostics are adjacent.	Evidence, OperationRun proof, and raw diagnostics are separated.

Repo-Truth Classification

Element in target image	Classification	Implementation note
Environment route and context	repo-verified	Existing route/screenshot anchor.
Backup/recovery widgets	repo-verified	Present in current report.
Readiness blocker lane	plausible-existing	Needs mapping to current signals.
Mutation-scope copy	foundation-only	Constitution-driven, exact UI not implemented.
Provider diagnostic drawer	conceptual-future-state	Must be separately verified.

Conceptual Elements Requiring Verification

Readiness blocker derivation
Evidence freshness source
Mutation scope wording
Provider diagnostics visibility

Implementation Notes

Later implementation should keep readiness, backup, recovery, operations, and governance as separate status dimensions.

Do Not Implement Blindly

Do not create a new environment health status family from the visual. Derive from existing truth or specify the behavior first.

2.2 KiB Raw Permalink Blame History