TenantAtlas/docs/ui-ux-enterprise-audit/target-images
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
..
problem-annotations Spec 325: add screenshot-anchored strategic target images (#385) 2026-05-18 07:18:13 +00:00
reference/spec-325-premium-reference Spec 325: add screenshot-anchored strategic target images (#385) 2026-05-18 07:18:13 +00:00
rejected/spec-325-initial-svg-pass Spec 325: add screenshot-anchored strategic target images (#385) 2026-05-18 07:18:13 +00:00
source Spec 325: add screenshot-anchored strategic target images (#385) 2026-05-18 07:18:13 +00:00
target Spec 325: add screenshot-anchored strategic target images (#385) 2026-05-18 07:18:13 +00:00
README.md Spec 325: add screenshot-anchored strategic target images (#385) 2026-05-18 07:18:13 +00:00

Spec 325 Target Images

This folder contains screenshot-anchored target images and sidecars for the Spec 325 strategic surface shortlist.

Structure

Path Purpose
target/ Accepted PNG target images and required sidecar Markdown files.
source/ Source screenshot policy notes. Current Spec 323 screenshots are reused by link instead of duplicated.
problem-annotations/ Reserved for future annotation images when a later spec needs them. Not used in Spec 325.
reference/spec-325-premium-reference/ User-accepted premium visual reference set used to calibrate the regenerated target PNGs.
rejected/spec-325-initial-svg-pass/ Rejected mockup policy and future rejected exploration holding area.

Premium Visual Reference

The accepted visual direction for Spec 325 is documented in reference/spec-325-premium-reference/README.md. The four reference images establish the premium dark shell, dense enterprise panel rhythm, table/detail workbench layout, and evidence/restore/governance visual language.

Those reference images are not implementation truth. They calibrate visual quality only; concrete data, dates, metrics, actions, and green success states still require repo verification before runtime implementation.

Accepted Target Images

Surface Dark target Light target Sidecar
Workspace Overview target/workspace-overview-target-dark.png target/workspace-overview-target-light.png target/workspace-overview-target.md
Environment Dashboard target/environment-dashboard-target-dark.png target/environment-dashboard-target-light.png target/environment-dashboard-target.md
Operations Hub target/operations-hub-target-dark.png target/operations-hub-target-light.png target/operations-hub-target.md
Governance Inbox target/governance-inbox-target-dark.png target/governance-inbox-target-light.png target/governance-inbox-target.md
Customer Review Workspace target/customer-review-workspace-target-dark.png target/customer-review-workspace-target-light.png target/customer-review-workspace-target.md
Audit Log target/audit-log-target-dark.png target/audit-log-target-light.png target/audit-log-target.md
Restore Safety Workflow target/restore-safety-workflow-target-dark.png target/restore-safety-workflow-target-light.png target/restore-safety-workflow-target.md
Provider Readiness target/provider-readiness-target-dark.png target/provider-readiness-target-light.png target/provider-readiness-target.md
Baseline Compare / Drift target/baseline-compare-drift-target-dark.png target/baseline-compare-drift-target-light.png target/baseline-compare-drift-target.md

Image Policy

  • Target images are design direction, not implementation truth.
  • Every image must be read with its target brief and sidecar.
  • The regenerated dark target images are the primary premium visual direction; light variants are compatibility/design-system support artifacts because Filament includes light mode by default.
  • Repo-verified elements may be treated as source anchors.
  • Conceptual elements must be verified in a later implementation spec.
  • Do not implement target images blindly.
  • Do not infer final brand system decisions from these images.