# V1-AWEB-105 — Explicit UX Signoff Criteria

Explicit signoff criteria for the Phase 17.10 admin redesign. Goal: **operator
trust, scan-speed, decision clarity, and safe action-taking** are observable and
testable.

This is the final ticket in Phase 17. It defines the bar that the redesigns
shipped in V1-AWEB-093 → V1-AWEB-104 must hit before the redesign is considered
"done" from a UX perspective.

## Operator trust

Trust is the reviewer's confidence that the surfaces in front of them are
accurate and that the actions they take will land as displayed.

- **TR-1.** Every provenance signal that can be presented as trustworthy /
  not-trustworthy is rendered via the `<ProvenanceTrustCard />` (V1-AWEB-097),
  with severity driven by the worst-of-four rule. Operators can answer "is this
  trustworthy?" in ≤ 2 seconds.
- **TR-2.** Every audit event is captured in the consolidated
  `<AuditTimeline />` (V1-AWEB-097); no decision is missing a timeline entry.
  The "copy-as-markdown" affordance (V1-AWEB-100) lets operators paste the
  timeline into a ticket without reformatting.
- **TR-3.** No banner or stripe animates on render (V1-AWEB-098). Operators
  report no "did the colour change?" doubt.
- **TR-4.** Confirmation modals never auto-focus the destructive action
  (V1-AWEB-099 Pattern 3). Operators cannot inadvertently confirm by hitting
  Enter.

## Scan speed

Scan speed is how quickly an operator can read a queue or detail surface and
identify the next item that needs action.

- **SS-1.** Severity stripe is the only emphasis on row text (V1-AWEB-095 +
  V1-AWEB-098). Operators can identify attention / urgent / critical rows at a
  glance without reading text.
- **SS-2.** Filter input parses `key:value` chunks (V1-AWEB-096); operators can
  narrow a 200-row queue to a 5-row triage in ≤ 5 seconds via typing.
- **SS-3.** Master-detail split (V1-AWEB-094) means the operator never loses
  queue context to inspect a row.
- **SS-4.** Density toggle (V1-AWEB-093) lets long-session operators trade
  vertical padding for visible row count without losing readability.

## Decision clarity

Decision clarity is the reviewer's certainty about which action to take and why.

- **DC-1.** Decision actions are always in the right-edge action rail
  (V1-AWEB-094) at ≥ 1280px; operators never scroll to find them.
- **DC-2.** Copilot suggestions render in a sibling card with a clear
  `match / override / ignore` affordance and never call the decision endpoint
  themselves (V1-AWEB-059 + V1-AWEB-064). Operators cannot mistake a copilot
  suggestion for a decision.
- **DC-3.** High-risk decisions require dual-confirmation + same-reviewer
  cooldown (V1-AWEB-063); the redesign preserves this behaviour and exposes it
  via `<AdminConfirmationModal />` typed confirmation.
- **DC-4.** Comparative reviews render with per-segment diff highlighting
  (V1-AWEB-097 `<TextDiff />`); operators can identify the difference between
  two competing texts without reading both end-to-end.

## Safe action-taking

Safe action-taking is the reviewer's confidence that the action will be executed
as intended and that destructive actions are guarded.

- **SA-1.** Every destructive action goes through `<AdminConfirmationModal />`
  Pattern 3 with a typed- confirmation control (V1-AWEB-099).
- **SA-2.** Bulk actions show a per-row progress indicator (V1-AWEB-100) so
  operators see partial-success state if a row fails.
- **SA-3.** No cross-workspace side effects from a single workspace action; an
  operator can revert a single-row decision via the inline "undo last"
  affordance on every decision panel that supports it.
- **SA-4.** RBAC denial is rendered consistently across all workspace panels
  (verified by every panel's RBAC denial E2E spec from V1-AWEB-085 / 086 / 087 /
  088 / 089).

## Signoff process

For each criterion above, the redesign is signed off only when:

1. The implementation tickets (V1-AWEB-093 → V1-AWEB-100) have shipped the
   relevant components.
2. The validation tickets (V1-AWEB-101 + V1-AWEB-102) have shown the criterion
   holds in real-operator validation.
3. The Playwright signoff suite (V1-AWEB-103) covers the criterion's observable
   behaviour.
4. The visual regression suite (V1-AWEB-104) protects the criterion's
   pixel-level rendering.

## Deliverables

This ticket's deliverable is this document itself. There is no code in
V1-AWEB-105; the implementation work landed in V1-AWEB-093 → V1-AWEB-104. The
signoff bar is held by:

- the V1-AWEB-101 keyboard validation report (after run);
- the V1-AWEB-102 extended-session validation report (after run);
- a green V1-AWEB-103 Playwright signoff suite;
- a green V1-AWEB-104 visual regression suite.

When all four are green and this document's criteria hold, the Phase 17.10
redesign is signed off; Phase 17 is complete.
