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

5.8 KiB

Baseline Compare / Drift Target Experience Brief

Metadata

Field Value
Surface ID UI-061
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 sidecar ../target-images/target/baseline-compare-drift-target.md
Primary persona Governance operator
Secondary personas Environment operator, manager, auditor
Repo-truth posture Route is repo-verified; browser review was blocked by fixture state. Target composition is direction only.

Current-State Snapshot

The route is present but local fixture variants returned 404, so the actual page was not evaluated in browser. The page remains strategic because it should show assignment, compare state, evidence gaps, and required governance action.

Current-State Productization Problems

  • Actual compare state was not browser-reviewed.
  • Assignment, latest result, evidence gaps, and next action need a target hierarchy.
  • Drift decision content must avoid raw diff noise as the first read.

Target User Promise

In five seconds, an operator knows what baseline this environment is compared against, what drift matters, and what decision is required.

First-Five-Seconds Target

Show assigned baseline, compare freshness, drift impact summary, evidence gaps, and one primary decision action.

Primary Decision

Review drift, accept exception, assign owner, or run compare.

Primary Action

Review drift impact.

Secondary Actions

Run compare, open baseline profile, inspect evidence gaps, create exception, open operation.

Target Information Hierarchy

  1. Environment and assigned baseline.
  2. Compare freshness and readiness.
  3. Drift impact summary.
  4. Required decision.
  5. Evidence gaps.
  6. Diff details and raw payloads.

Main-View Keep / Promote / Simplify

Treatment Elements
Keep Environment route, baseline assignment, compare result, operation link.
Promote Drift impact, evidence gap, owner/action, compare recency.
Simplify Raw diff rows, low-level setting IDs, generic success/failure badges.

Detail Drawer Treatment

Drift drawer should show affected policy/control, expected vs observed, impact, evidence, owner, and decision actions. Raw diff JSON stays collapsed.

Advanced/Admin Treatment

Baseline reassignment, capture, compare now, and exception actions need authorization, confirmation where high impact, audit, and OperationRun continuity.

Hidden/Removed Default Elements

Hide raw JSON diffs, internal setting IDs, provider payloads, and unsupported compliance claims from first view.

Target Layout Direction

Use a drift decision workbench: baseline context header, compare readiness strip, impact clusters, evidence gaps, and detail drawer.

Visual Target Direction

Dark governance surface with amber for review-needed drift, coral for blocked/unsafe gaps, violet evidence links, and mint only for verified compare readiness or permitted actions.

Status/Trust Model

Separate assignment state, compare freshness, drift severity, evidence completeness, and operation execution state.

Dangerous Actions

Compare now, capture baseline, assign baseline, or accept exception are high impact. Later implementation must enforce authorization, confirmation where required, audit, and OperationRun links.

Customer-Safe Review Notes

Customer-facing summaries should explain impact and accepted risk without raw diff details or internal reason families.

Workspace/Environment Context

Workspace and environment are visible. The target baseline and source of comparison must be explicit before actions.

Empty / Loading / Error States

Empty state should explain that no baseline assignment or compare result is available and offer one safe setup or compare action. Loading preserves environment context. Error state distinguishes unauthorized/not-found from missing compare data.

Accessibility Notes

Drift severity and evidence gap state need text labels. Diff drawers must preserve keyboard navigation.

Repo-Truth Classification

Target element Classification Notes
Baseline compare route repo-verified Route is present, fixture returned 404.
BaselineProfile and OperationRun concepts repo-verified Existing model inventory includes both.
Drift impact clusters plausible-existing Must map to actual compare output later.
Evidence gap scoring foundation-only Product direction only until data mapping is verified.
Exception workflow from compare drawer conceptual-future-state Must be separately specified.

Screenshot-Anchored Image Prompt

Start from ui-015-baseline-compare-blocked-404.png as blocked current evidence. Create a target design direction, not runtime implementation. Preserve environment baseline compare purpose. Show assigned baseline, compare freshness, drift impact, evidence gaps, primary Review drift impact action, secondary Run compare action, OperationRun proof link, and collapsed raw diff detail. Avoid generic SaaS dashboards, fake compliance claims, green success without verification, placeholder text, raw diff noise as default, and runtime implementation claims.

Implementation Pattern Requirements

  • Environment and assigned baseline are visible before actions.
  • Drift impact appears before raw diff.
  • Compare/run links use OperationRun patterns.
  • Customer-safe summaries hide raw provider payloads.

Later Implementation Candidate

Drift/Baseline decision experience.

Non-Goals For Later Implementation

Do not invent new drift states, evidence scores, or exception workflows without repo/data verification and a separate spec if needed.