TenantAtlas/docs/ui-ux-enterprise-audit/target-images/target/baseline-compare-drift-target.md
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

Baseline Compare / Drift 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.

Item Link
Source route /admin/workspaces/{workspace}/environments/{environment}/baseline-compare
Source screenshot ../../screenshots/desktop/ui-015-baseline-compare-blocked-404.png
Source page report ../../page-reports/ui-015-baseline-compare.md
Target brief ../../target-experience-briefs/baseline-compare-drift.md
Dark target image baseline-compare-drift-target-dark.png
Light target image baseline-compare-drift-target-light.png

Transformation Table

Current state Target direction
Browser fixture returned 404 for the compare route. Target is bounded to route-verified compare/readiness guidance.
Raw diff risk can dominate first read. Drift impact and evidence gaps lead before raw diff.
Assignment, freshness, and operation truth need separation. Baseline, compare freshness, evidence gap, and run proof are distinct.

Repo-Truth Classification

Element in target image Classification Implementation note
Baseline compare route repo-verified Route exists, fixture blocked.
BaselineProfile and OperationRun concepts repo-verified Existing models.
Drift impact clusters plausible-existing Must map to compare result data.
Evidence gap scoring foundation-only Product direction only.
Exception workflow from drawer conceptual-future-state Separate spec required.

Conceptual Elements Requiring Verification

  • Baseline assignment data source
  • Compare freshness calculation
  • Drift impact grouping
  • Evidence gap display and customer-safe wording

Implementation Notes

Later implementation should put impact before raw diff and keep compare actions authorized, audited, and OperationRun-backed.

Do Not Implement Blindly

Do not invent drift scores, evidence scores, or exception workflows from this visual.