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

Governance Inbox 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/governance/inbox`
Source screenshot	`../../screenshots/desktop/ui-004-governance-inbox.png`
Source page report	`../../page-reports/ui-004-governance-inbox.md`
Target brief	`../../target-experience-briefs/governance-inbox.md`
Dark target image	`governance-inbox-target-dark.png`
Light target image	`governance-inbox-target-light.png`

Transformation Table

Current state	Target direction
Decision queue intent exists but first action can blur.	One priority decision and Review decision action anchor the page.
Evidence and status dimensions can blend.	Reason, impact, owner, due state, and evidence basis are distinct.
Customer-safe downstream copy is not explicit.	Customer-safe summary is visible but diagnostics stay hidden.

Repo-Truth Classification

Element in target image	Classification	Implementation note
Governance route and screenshot	repo-verified	Existing route/screenshot anchor.
Decision queue purpose	repo-verified	Current report confirms purpose.
Recommended next action	plausible-existing	Needs domain mapping.
Customer-safe summary	foundation-only	Requires copy/data review.
Unified decision taxonomy	conceptual-future-state	Do not create without separate spec.

Conceptual Elements Requiring Verification

Recommended action logic
Decision owner and due-state source
Customer-safe summary
Mutating action confirmation/audit behavior

Implementation Notes

Later implementation should keep exactly one dominant next decision action and use evidence-first detail drawers.

Do Not Implement Blindly

Do not create new decision status families or taxonomies from target image labels alone.

2.1 KiB Raw Blame History