docs(ui): enrich component preservation map
This commit is contained in:
master
@@ -4,7 +4,6 @@
|
||||
- `docs/implplan/SPRINT_20260221_041_FE_prealpha_ia_ops_setup_rewire.md`
|
||||
- `docs/implplan/SPRINT_20260307_004_FE_self_serve_search_answer_first.md`
|
||||
- `docs/implplan/SPRINT_20260307_006_FE_self_serve_rollout_and_gap_closure.md`
|
||||
- `docs/implplan/SPRINT_20260307_009_DOCS_ui_component_preservation_map.md`
|
||||
- `docs/implplan/SPRINT_20260307_023_DOCS_ui_restoration_topic_shapes.md`
|
||||
|
||||
## Delivery Tasks
|
||||
@@ -54,7 +53,7 @@
|
||||
- [DONE] DOCS-UCM-001 UI component preservation map scaffold and inventory
|
||||
- [DONE] DOCS-UCM-002 First-pass preservation judgments for unused and weakly surfaced UI components
|
||||
- [DONE] DOCS-UCM-003 Summary tree for keep / merge / wire / archive decisions
|
||||
- [TODO] DOCS-UCM-004 Deep enrichment against Stella Ops product and module docs
|
||||
- [DONE] DOCS-UCM-004 Deep enrichment against Stella Ops product and module docs
|
||||
- [DONE] DOCS-UCM-005 Ordered restoration backlog for dropped functionality topics
|
||||
- [DONE] DOCS-RTS-001 Restoration topic index and placement rules
|
||||
- [DONE] DOCS-RTS-002 Watchlist restoration placement note
|
||||
|
||||
@@ -117,3 +117,5 @@ Generated on 2026-03-07. This map captures Angular components that currently loo
|
||||
- This is a first-pass map. The weak-route bucket especially needs follow-up review against relative tab navigation and Stella Ops product docs.
|
||||
- Per-component dossiers are intentionally stable so later iterations can deepen the judgment rather than recreate the inventory.
|
||||
- The accepted Tier 1 restoration topics now have implementation-ready UX dossiers and FE sprint files under `docs/modules/ui/` and `docs/implplan/`.
|
||||
- High-value dead branches now include corroborating links back to current Stella Ops dossiers, runbooks, contracts, or route-migration docs so the keep/merge/wire decisions are grounded in product documentation, not just frontend reachability scans.
|
||||
- The remaining explicit `investigate` set is now concentrated in the generic/ambiguous buckets rather than the clearly product-shaped branches: `Advisory Ai`, `Lineage`, `Security Explorer` variants, `Evidence / Proof` variants, and miscellaneous prototype shells such as `Snapshot`, `Timeline`, `Scores`, `Dashboard`, and `Workspaces`.
|
||||
|
||||
@@ -14,6 +14,12 @@ Keep the authoring concepts, simulation affordances, approvals flow, and any edi
|
||||
## Likely Destination
|
||||
/admin/policy/governance and /admin/policy/simulation
|
||||
|
||||
## Corroborating Docs
|
||||
- Current UI owner and merge target: `../../../../policy-decisioning-studio/README.md`
|
||||
- Policy engine product/module dossier: `../../../../../policy/README.md`
|
||||
- Policy authoring and governance workflow: `../../../../../contracts/policy-studio.md`
|
||||
- Evaluation and release-gate flow context: `../../../../../flows/04-policy-evaluation-flow.md`
|
||||
|
||||
## Components
|
||||
- [ConflictVisualizerComponent](../features/policy-studio/ai/ConflictVisualizerComponent.md) - `merge`, features/policy-studio/ai/conflict-visualizer.component.ts
|
||||
- [LiveRulePreviewComponent](../features/policy-studio/ai/LiveRulePreviewComponent.md) - `merge`, features/policy-studio/ai/live-rule-preview.component.ts
|
||||
|
||||
@@ -14,6 +14,12 @@ Keep witness capture, proof overlays, and explainability flows that can reinforc
|
||||
## Likely Destination
|
||||
/security/reachability or /evidence
|
||||
|
||||
## Corroborating Docs
|
||||
- Current UI owner and route contract: `../../../../reachability-witnessing/README.md`
|
||||
- Reachability product and evidence model: `../../../../../reachability/README.md`
|
||||
- Operator troubleshooting runbook: `../../../../../operations/reachability-runbook.md`
|
||||
- Runtime and proof workflow context: `../../../../../operations/runbooks/reachability-runtime.md`
|
||||
|
||||
## Components
|
||||
- [PoEDrawerComponent](../features/reachability/PoEDrawerComponent.md) - `merge`, features/reachability/poe-drawer.component.ts
|
||||
- [WitnessPageComponent](../features/reachability/WitnessPageComponent.md) - `merge`, features/reachability/witness-page.component.ts
|
||||
|
||||
@@ -14,6 +14,12 @@ Keep any explainability, quiet-lane, or audit-bundle interactions that meaningfu
|
||||
## Likely Destination
|
||||
/triage/artifacts or /evidence
|
||||
|
||||
## Corroborating Docs
|
||||
- Current UI owner and merge target: `../../../../triage-explainability-workspace/README.md`
|
||||
- Triage API/contract surface: `../../../../../api/triage.contract.v1.md`
|
||||
- Unified triage product specification: `../../../../../modules/web/unified-triage-specification.md`
|
||||
- Platform explainable-triage implementation context: `../../../../../modules/platform/explainable-triage-implementation-plan.md`
|
||||
|
||||
## Components
|
||||
- [AiRecommendationWorkbenchComponent](../features/triage/AiRecommendationWorkbenchComponent.md) - `merge`, features/triage/ai-recommendation-workbench.component.ts
|
||||
- [AiCodeGuardBadgeComponent](../features/triage/components/ai-code-guard-badge/AiCodeGuardBadgeComponent.md) - `merge`, features/triage/components/ai-code-guard-badge/ai-code-guard-badge.component.ts
|
||||
|
||||
@@ -14,5 +14,11 @@ Keep conflict resolution workflows, rationale capture, and consensus tooling tha
|
||||
## Likely Destination
|
||||
/admin/vex-hub
|
||||
|
||||
## Corroborating Docs
|
||||
- Current UI owner and merge target: `../../../../policy-decisioning-studio/README.md`
|
||||
- Canonical VEX owner module: `../../../../../vex-hub/README.md`
|
||||
- VEX trust and evidence linkage in policy: `../../../../../policy/guides/vex-trust-model.md`
|
||||
- VEX operations/runbook context: `../../../../../operations/runbooks/vex-ops.md`
|
||||
|
||||
## Components
|
||||
- [VexConflictStudioComponent](../features/vex-studio/VexConflictStudioComponent.md) - `merge`, features/vex-studio/vex-conflict-studio.component.ts
|
||||
|
||||
@@ -14,5 +14,10 @@ Keep the operational watchlist concept, status views, and monitoring workflows;
|
||||
## Likely Destination
|
||||
/mission-control or /ops
|
||||
|
||||
## Corroborating Docs
|
||||
- Current UI owner and route contract: `../../../../watchlist-operations/README.md`
|
||||
- Identity watchlist operator guide: `../../../../../attestor/guides/identity-watchlist.md`
|
||||
- Monitoring and alert-response runbook: `../../../../../operations/watchlist-monitoring-runbook.md`
|
||||
|
||||
## Components
|
||||
- [WatchlistPageComponent](../features/watchlist/WatchlistPageComponent.md) - `wire-in`, features/watchlist/watchlist-page.component.ts
|
||||
|
||||
@@ -14,6 +14,11 @@ Keep the timeline, step-diff, and replay ideas if they can strengthen evidence o
|
||||
## Likely Destination
|
||||
/evidence or /releases/runs
|
||||
|
||||
## Corroborating Docs
|
||||
- Current UI owner and route contract: `../../../../workflow-visualization-replay/README.md`
|
||||
- Release-gate and evidence workflow dossier: `../../../../../release-orchestrator/workflow/evidence-based-release-gates.md`
|
||||
- Release/workflow trigger model: `../../../../../technical/cicd/workflow-triggers.md`
|
||||
|
||||
## Components
|
||||
- [StepDetailPanelComponent](../features/workflow-visualization/components/step-detail-panel/StepDetailPanelComponent.md) - `investigate`, features/workflow-visualization/components/step-detail-panel/step-detail-panel.component.ts
|
||||
- [TimeTravelControlsComponent](../features/workflow-visualization/components/time-travel-controls/TimeTravelControlsComponent.md) - `investigate`, features/workflow-visualization/components/time-travel-controls/time-travel-controls.component.ts
|
||||
|
||||
@@ -10,7 +10,6 @@ Provide a living plan for UI deliverables, dependencies, and evidence.
|
||||
## Near-term deliverables
|
||||
- `SPRINT_20260307_004_FE_self_serve_search_answer_first.md` - answer-first search shell, page-owned self-serve questions, and explicit fallback states.
|
||||
- `SPRINT_20260307_006_FE_self_serve_rollout_and_gap_closure.md` - page rollout, guided handoffs, and telemetry-driven gap closure.
|
||||
- `SPRINT_20260307_009_DOCS_ui_component_preservation_map.md` - per-component preservation dossiers for unused and weakly surfaced console UI components.
|
||||
- `SPRINT_20260307_023_DOCS_ui_restoration_topic_shapes.md` - documentation prerequisite for shell/menu/tab placements; not a product-delivery sprint by itself.
|
||||
|
||||
## Latest evidence
|
||||
|
||||
Reference in New Issue
Block a user