ahmido
4cf2712f92
Implemented the first version of the operator resolution guidance framework. Added new foundation classes (ResolutionCase, ResolutionAction) and a ReviewPackOutputResolutionAdapter. Updated the Customer Review Workspace and Environment Review Resource to use the new adapter. Added extensive test coverage for the framework and UI integrations. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #421
53 lines
2.6 KiB
Markdown
53 lines
2.6 KiB
Markdown
# UI-040 Environment Review Detail
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Route | `/admin/workspaces/{workspace}/environments/{environment}/environment-reviews/{record}` |
|
|
| Source | `EnvironmentReviewResource::view` |
|
|
| Area / scope | Reviews / environment detail |
|
|
| Archetype | Evidence / Audit |
|
|
| Design depth | Strategic Surface |
|
|
| Repo truth | repo-verified |
|
|
| Screenshot | `Spec 350 browser proof: specs/350-operator-resolution-guidance-framework-v1/artifacts/screenshots/02-detail-context.png` |
|
|
| Browser status | Reached through direct environment route and customer-workspace handoff. |
|
|
|
|
## First Five Seconds
|
|
|
|
The page should answer three questions without forcing the operator to reconstruct the review from raw sections:
|
|
|
|
1. what is the review status
|
|
2. what is the output readiness
|
|
3. what is the safe next step
|
|
|
|
## Productization Review
|
|
|
|
- Decision-first: improved by the shared resolution-case summary.
|
|
- Evidence-first: limitations and technical details remain visible below the summary.
|
|
- Context: environment-bound review detail with optional customer-workspace handoff context.
|
|
- Customer/auditor safety: high because this page explains whether the current released output is share-safe.
|
|
- Diagnostics: sections and raw detail stay secondary to the first-screen output guidance.
|
|
|
|
## Information Inventory
|
|
|
|
Default content should show lifecycle status, output guidance, publication/sharing boundary, evidence snapshot linkage, current export linkage, and section completeness.
|
|
|
|
## Dangerous Actions
|
|
|
|
Lifecycle actions such as refresh, publish, export, create-next-review, and archive remain source-owned. In customer-workspace detail mode, the repeated primary action rail should stay suppressed so the operator does not get duplicate or conflicting calls to action.
|
|
|
|
## Spec 349 Follow-up
|
|
|
|
Spec 349 separated review status, output readiness, and publication/sharing state while keeping the customer-workspace detail mode free of repeated CTA rails.
|
|
|
|
## Spec 350 Follow-up
|
|
|
|
Spec 350 adds the shared review-output resolution-case handoff:
|
|
|
|
- the first-screen summary now uses the same issue / reason / impact / next-action reading direction as the workspace
|
|
- source refs and evidence refs remain repo-backed in the underlying contract
|
|
- customer-workspace detail mode still suppresses repeated action buttons and keeps the limitations/technical-details path as the primary inspection flow
|
|
|
|
## Target Direction
|
|
|
|
Keep this surface audit- and evidence-oriented. If future work broadens it beyond the review-output path, that should happen through a dedicated detail-surface spec rather than hidden incremental drift.
|