d71493f82a
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 4m44s
Added BaselineReadinessGate, resolution propagation, and disclosure semantics logic per Spec 385. Integrated baseline unreadiness into Customer Review Workspace and Review Packs.
57 lines
2.1 KiB
Markdown
57 lines
2.1 KiB
Markdown
# UI-011 Review Register
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Route | `/admin/reviews` |
|
|
| Source | `ReviewRegister` |
|
|
| Area / scope | Reviews / workspace |
|
|
| Archetype | Reviews |
|
|
| Design depth | Strategic Surface |
|
|
| Repo truth | repo-verified |
|
|
| Screenshot | `../screenshots/desktop/ui-011-reviews.png` |
|
|
| Browser status | Reached through workspace route. |
|
|
|
|
## First Five Seconds
|
|
|
|
The page is a review register. It should help an operator understand review readiness, open work, evidence basis, publication state, and customer-facing outputs without requiring detail-page reconstruction.
|
|
|
|
## Productization Review
|
|
|
|
- Decision-first: medium.
|
|
- Evidence-first: should link to evidence/review packs.
|
|
- Context: workspace hub.
|
|
- Customer/auditor safety: high because review outputs become customer-facing.
|
|
- Diagnostics: review internals should stay below outcome/readiness.
|
|
|
|
## Information Inventory
|
|
|
|
Default content should show review subject, lifecycle, readiness, evidence freshness, accepted risk state, and next action.
|
|
|
|
## Dangerous Actions
|
|
|
|
Publish, export, review-pack generation, or close actions are high-impact and must preserve auditability and confirmation where applicable.
|
|
|
|
## 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
|
|
|
|
1. Review readiness needs a first-class summary.
|
|
2. Customer-safe output state should be obvious.
|
|
3. Evidence freshness and accepted-risk visibility need consistent patterns.
|
|
|
|
## Target Direction
|
|
|
|
P1 strategic target paired with the Customer Review Workspace target.
|
|
|
|
## Spec 385 Follow-up
|
|
|
|
Spec 385 updates review readiness truth without adding a new register route.
|
|
|
|
- baseline readiness blockers from the baseline drift section feed the existing publish blockers summary
|
|
- partial baseline sections remain publishable only when they carry disclosed limitations and no customer-ready blocker
|
|
- trusted drift is visible as review findings and does not demote the register state to blocked by itself
|