# UI-003 Operations

| Field | Value |
| --- | --- |
| Route | `/admin/workspaces/{workspace}/operations` |
| Source | `Operations`, `OperationRunLinks` |
| Area / scope | Monitoring / workspace |
| Archetype | Operations / Monitoring |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | `../screenshots/desktop/ui-003-operations.png` |
| Browser status | Reached through local workspace route. |

## First Five Seconds

The page reads as an operations monitor with decision-first follow-up. It exposes run scope, lifecycle/outcome truth, and one safe next action before operators move into diagnostics. The history table now compresses secondary fields below wide desktop widths so the core decision columns remain visible.

## Productization Review

- Decision-first: high; run rows and detail summaries surface a resolver-owned safe next action and concise attention context.
- Evidence-first: OperationRun records are the source.
- Context: workspace route is explicit.
- Customer/auditor safety: not customer-facing by default.
- Diagnostics: secondary; raw/support context remains gated behind detail/diagnostic affordances.

## Information Inventory

The page exposes run state, status, scope, recent work, attention reason, and safe next action. Execution outcome is visible; governance result and artifact truth remain separate surfaces and related artifacts are opened through canonical OperationRun links. In the history table, operation context absorbs status/scope/timing on constrained widths while secondary columns remain available on wider screens.

## Dangerous Actions

Potential actions are intentionally constrained to inspect/open related artifacts or a confirmation-gated Reconcile action. Retry remains unavailable unless a repo-verified safe seam exists, and high-risk restore/promotion states must not expose retry, re-execute, force-complete, mark-succeeded, delete, or purge controls.

## Scores

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

## Top Issues

1. Execution truth must stay visually separate from product health.
2. Detail drilldowns must keep evidence/result links canonical and scope-safe.
3. Wider-screen target composition should still evolve toward a true attention queue plus proof rail, but the current table no longer requires horizontal scanning for the core decision on constrained desktop widths.

## Target Direction

P1 strategic target. Use one monitoring pattern for active, failed, partial, and completed runs, with safe next actions and evidence/result links delegated to shared OperationRun UX contracts.