ahmido
54eb8ca065
Added a decision-first section to the Baseline Profile detail page. Includes request caching for summary metrics and corresponding browser/feature tests. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #440
2.4 KiB
UI-010 Baseline Profiles
| Field | Value |
|---|---|
| Route | /admin/baseline-profiles |
| Source | BaselineProfileResource |
| Area / scope | Governance / workspace-owned analysis |
| Archetype | Drift / Diff |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | ../screenshots/desktop/ui-010-baseline-profiles.png |
| Browser status | Reached through workspace route. |
First Five Seconds
The page is a baseline library. It needs to make the reusable standard, snapshot truth, assignment state, and compare readiness clearer than a generic admin resource.
Productization Review
- Decision-first: medium; library behavior is visible but product purpose needs clearer framing.
- Evidence-first: snapshot and compare links should be central.
- Context: workspace-owned, not environment shell.
- Customer/auditor safety: not directly customer-facing.
- Diagnostics: capture/compare evidence should be available on demand.
Spec 369 Detail Update
The Baseline Profile detail page now opens with a Decision section before profile metadata or governed-subject normalization detail. The first read answers readiness, decision reason, operational impact, snapshot basis, assignment usefulness, and one dominant next action while keeping Baseline truth and Related context immediately below it.
Screenshot evidence: ../../specs/369-baseline-profile-decision-view/artifacts/screenshots/decision-first-detail.png.
Information Inventory
Default content should include profile status, capture mode, latest snapshot, assignment count, compare posture, and next action.
Dangerous Actions
Capture, compare, archive, and baseline assignment changes are high impact. They need confirmation, authorization, audit, and OperationRun continuity.
Scores
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 3 | 4 | 3 | 4 | 3 | 3 | 4 | 3 | 3 | 4 | 3 | 4 |
Top Issues
- Generic resource feel hides the product role of baselines.
- Snapshot truth and assigned-environment impact need stronger hierarchy. Spec 369 improves this on the detail page.
- Dangerous capture/compare actions need target-state review.
Target Direction
P1 strategic target for governance baseline library and domain pattern for related create/edit/detail pages.