4.1 KiB
4.1 KiB
Restoration Topic Shapes
This directory turns the top restoration candidates into concrete product shapes.
It answers four questions for each topic:
- Is this a standalone product, a submenu, a tabbed area, or a contextual tool?
- Where should it live in the current Stella Ops IA?
- Which dropped or weakly surfaced components should be merged into it?
- Where do single actions, panels, and stray pages go if they do not deserve their own product?
Topic Index
- Watchlist
- Reachability Witnessing
- Platform Ops Consolidation
- Triage Explainability Workbench
- Workflow Visualization And Replay
Detailed UX Dossiers
- Identity Watchlist
- Reachability Witnessing
- Platform Ops Consolidation
- Triage Explainability Workspace
- Workflow Visualization And Replay
- Contextual Actions And Stray Surfaces
Implementation Sprint Set
docs-archived/implplan/SPRINT_20260307_024_FE_identity_watchlist_shell.md- shipped watchlist restorationdocs/implplan/SPRINT_20260307_025_FE_reachability_witnessing_merge.mddocs/implplan/SPRINT_20260307_026_FE_platform_ops_consolidation.mddocs/implplan/SPRINT_20260307_027_FE_triage_explainability_workspace.mddocs/implplan/SPRINT_20260307_028_FE_workflow_visualization_replay.mddocs/implplan/SPRINT_20260307_029_FE_contextual_actions_and_stray_surfaces.md
Placement Matrix
| Topic | Recommended shape | Primary menu placement | Primary tabs / submenus |
|---|---|---|---|
| Watchlist | Narrow operational shell, not standalone product | Setup > Trust & Signing |
Entries, Alerts, Tuning |
| Reachability Witnessing | Merge into existing security feature | Security > Reachability |
Coverage, Witnesses, PoE / Exposure, Sensor Gaps |
| Platform Ops Consolidation | Consolidated ops shell | Ops > Operations |
Data Integrity, Jobs & Queues, Health & SLO, Feeds & Airgap, Quotas, AOC, Diagnostics |
| Triage Explainability Workbench | Merge into triage workspace | Triage > Artifact Workspace and Triage > Audit Bundles |
list tabs for lanes; right-rail explainability tabs in detail view |
| Workflow Visualization And Replay | Contextual runtime view, not standalone product | Releases > Runs and Evidence > Verify & Replay |
Summary, Graph, Timeline, Replay, Evidence |
Placement Rules For Stray Pages And Single Actions
Use these rules when a dropped surface has value but does not deserve its own top-level product.
1. Configurable capability with low daily traffic
- Put it under the owning admin/setup area as a submenu or tab.
- Example: watchlist entry management belongs under trust/signing setup, not as a top-level product.
2. Operator workflow with one dominant list/detail loop
- Put the list in the parent product and make advanced tools tabs, drawers, or right-rail panels.
- Example: quiet-lane and AI recommendation flows belong inside triage list/detail pages.
3. Explanation or evidence for an existing decision
- Make it contextual to the owning workflow, usually a detail tab or drawer.
- Example: witness view and PoE belong under reachability, findings, or release-context evidence.
4. Runtime graph or replay view
- Put it on the run detail page first, with optional evidence-side entry points.
- Example: workflow visualization should be a run-detail tab, not a separate sidebar product.
5. Cross-cutting operational utilities
- Keep one consolidated ops overview and route tree.
- Do not create a second ops product when grouped cards and subroutes are enough.