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

Provider Readiness 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/provider-connections` plus create/detail family
Source screenshot	`../../screenshots/desktop/ui-009-provider-connections.png`
Source page report	`../../page-reports/ui-009-provider-connections.md`
Target brief	`../../target-experience-briefs/provider-readiness.md`
Dark target image	`provider-readiness-target-dark.png`
Light target image	`provider-readiness-target-light.png`

Transformation Table

Current state	Target direction
Provider table needs stronger readiness hierarchy.	Readiness, permission gaps, verification, and next action lead.
Raw integration details can dominate.	Diagnostics are collapsed and redacted.
Dangerous actions need safety posture.	Rotate, disconnect, and re-consent actions require confirmation/audit notes.

Repo-Truth Classification

Element in target image	Classification	Implementation note
Provider route and screenshot	repo-verified	Existing route/screenshot anchor.
ProviderConnection model	repo-verified	Existing model.
Permission readiness summary	plausible-existing	Needs mapping to existing contracts/permissions.
Capability impact copy	foundation-only	Requires deterministic capability mapping.
Multi-provider neutral language	spec-only	Product direction for later implementation.

Conceptual Elements Requiring Verification

Permission gap source
Capability impact mapping
Credential lifecycle status
Re-consent and rotation action rules

Implementation Notes

Later implementation should keep provider-specific semantics bounded and never expose secrets or raw credential payloads.

Do Not Implement Blindly

Do not create a provider framework or new provider taxonomy from this image.

2.1 KiB Raw Permalink Blame History