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.1 KiB

Raw Permalink Blame History

Operations Hub 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}/operations`
Source screenshot	`../../screenshots/desktop/ui-003-operations.png`
Source page report	`../../page-reports/ui-003-operations.md`
Target brief	`../../target-experience-briefs/operations-hub.md`
Dark target image	`operations-hub-target-dark.png`
Light target image	`operations-hub-target-light.png`

Transformation Table

Current state	Target direction
Chronological run history is the dominant shape.	Attention-needed runs and active progress lead the page.
Execution truth can be mistaken for governance health.	Execution state, outcome, and evidence are visually separated.
Raw diagnostics can become primary detail.	Raw/support diagnostics remain collapsed behind proof summary.

Repo-Truth Classification

Element in target image	Classification	Implementation note
Operations route	repo-verified	Existing route/screenshot anchor.
OperationRun records	repo-verified	Existing model and current page purpose.
Attention-needed grouping	plausible-existing	Derive from status/outcome in later spec.
Artifact proof rail	foundation-only	Requires per-operation artifact mapping.
Retry/cancel action set	unknown	Must be verified by operation family.

Conceptual Elements Requiring Verification

Run grouping logic
Summary count labels
Retry/cancel availability
Artifact link resolution and entitlement

Implementation Notes

Later implementation should reuse the central OperationRun UX contract and keep terminal notifications, run links, and artifact links consistent.

Do Not Implement Blindly

Do not introduce local OperationRun semantics or duplicate notification paths from this image.

2.1 KiB Raw Permalink Blame History