ahmido
39298f27f2
Added `BaselineSubjectResolution` page and supporting logic to visualize missing identities, ambiguous matches, and skipped coverages as defined in Spec 384. Replaces legacy compare warnings with an actionable, deterministic UI surface. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #455
3.1 KiB
UI-100 Baseline Subject Resolution
| Field | Value |
|---|---|
| Route | /admin/workspaces/{workspace}/environments/{environment}/baseline-subject-resolution |
| Source | BaselineSubjectResolution |
| Area / scope | Governance / environment |
| Archetype | Drift / Diff |
| Design depth | Strategic Surface |
| Repo truth | browser-verified route; feature-tested |
| Screenshot | desktop, bind modal, mobile |
| Browser status | Browser smoke passed for route reachability, scoped worklist content, bind-modal copy, and narrow viewport overflow. |
First Five Seconds
The page should read as a focused decision queue for baseline subjects that need identity binding or coverage decisions. It must make the active environment, source compare run, problem category, readiness impact, and available candidates visible before any action.
Productization Review
- Decision-first: operators see actionable subjects, readiness impact, actionability, candidates, and current decision state before raw evidence.
- Evidence-first: source operation and provider/resource metadata remain available but not dominant.
- Context: environment-bound route with workspace/environment scope enforced before rendering.
- Customer/auditor safety: high, because decisions affect future baseline compare interpretation.
- Diagnostics: raw provider identifiers and fingerprints stay secondary and truncated/collapsed by default.
Information Inventory
Default content shows summary counts, active source run, actionable subject rows, provider/class/type filters, readiness/actionability/reason filters, candidate availability, current binding/decision state, and source/run links.
Dangerous Actions
Manual binding, decision recording, revocation, and rerun compare are high-impact. They require confirmation, capability enforcement, server-side authorization, operator notes where persisted decisions are written, and audit logging through the existing binding service or OperationRun flow.
Scores
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 7 | 7 | 7 | 6 | 7 | 7 | 7 | 6 | 6 | 7 | 7 | 7 |
Top Issues
- The compact decision modals should be rechecked visually if additional decision modes add more fields.
- Follow-up iteration should add richer audit-history disclosure if operator volume grows.
- The current V1 table uses inline context plus action modals rather than a separate detail route.
Target Direction
Keep this as a scoped operator worklist rather than a broad governance landing page. Preserve the TenantPilot-only decision boundary, route-bound environment context, and compare/run entry links.