# UI-015 Baseline Compare

| Field | Value |
| --- | --- |
| Route | `/admin/workspaces/{workspace}/environments/{environment}/baseline-compare` |
| Source | `BaselineCompareLanding` |
| Area / scope | Governance / environment |
| Archetype | Drift / Diff |
| Design depth | Strategic Surface |
| Repo truth | repo-verified route; browser blocked |
| Screenshot | `../screenshots/desktop/ui-015-baseline-compare-blocked-404.png` |
| Browser status | Route is present in route list, but the local Spec 180 fixture returned 404 for tested environment variants. |

## First Five Seconds

The browser pass could not evaluate the actual Baseline Compare page. Spec 319 made this page environment-owned, so it remains strategic even though this fixture could not render it.

## Productization Review

- Decision-first: not evaluated in browser.
- Evidence-first: expected to show assignment, compare state, evidence gaps, and next action.
- Context: environment-bound route required.
- Customer/auditor safety: medium/high because compare posture feeds governance decisions.
- Diagnostics: raw compare evidence should be progressive.

## Information Inventory

Expected default content should show selected environment, assigned baseline, compare readiness, latest result, gaps, operation links, and recommended action.

## Dangerous Actions

Compare now and baseline assignment/capture actions are high-impact and must keep confirmation, authorization, audit, and OperationRun links.

## Scores

| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |

## Top Issues

1. Browser review blocked for available fixture.
2. Environment-owned route must remain visibly route-bound.
3. Assignment, compare, and evidence-gap truth need target hierarchy.

## Target Direction

P1 individual target mockup after a suitable baseline fixture exists.