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

docs-archive/implplan/SPRINT_20260307_024_FE_identity_watchlist_shell.md - shipped watchlist restoration
docs-archive/implplan/SPRINT_20260307_025_FE_reachability_witnessing_merge.md - shipped reachability witnessing restoration
docs-archive/implplan/SPRINT_20260307_026_FE_platform_ops_consolidation.md - shipped platform ops consolidation
docs-archive/implplan/SPRINT_20260307_027_FE_triage_explainability_workspace.md - shipped triage explainability restoration
docs-archive/implplan/SPRINT_20260307_028_FE_workflow_visualization_replay.md - shipped workflow visualization and replay restoration
docs-archive/implplan/SPRINT_20260307_029_FE_contextual_actions_and_stray_surfaces.md - shipped shared contextual primitives

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`

Use these rules when a dropped surface has value but does not deserve its own top-level product.

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.

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.

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.

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.