docs(ui): archive restoration topic shapes sprint

docs-archived/implplan/SPRINT_20260307_023_DOCS_ui_restoration_topic_shapes.md

@@ -0,0 +1,136 @@
+# Sprint 20260307-023 - UI Restoration Topic Shapes
+
+## Topic & Scope
+- Convert the highest-confidence restoration topics after Decisioning Studio into concrete product-shape notes.
+- For each topic, define whether it should be a submenu, tabbed shell, contextual drawer, or reusable detail page.
+- Explicitly place stray pages and single actions into the active Stella Ops IA instead of reviving orphan products.
+- This is a documentation prerequisite sprint only; it does not count as shipping the restored functionality by itself.
+- Working directory: `docs/modules/ui/restoration-topics`.
+- Allowed coordination edits: `docs/implplan/`, `docs/modules/ui/TASKS.md`, `docs/modules/ui/implementation_plan.md`, and `docs/modules/ui/component-preservation-map/README.md`.
+- Expected evidence: restoration topic index, five topic notes, placement rules, and cross-links from the preservation map.
+
+## Dependencies & Concurrency
+- Depends on:
+  - `docs/modules/ui/component-preservation-map/RESTORATION_PRIORITIES.md`
+  - `docs/modules/ui/component-preservation-map/SUMMARY_TREE.md`
+  - `docs/modules/ui/policy-decisioning-studio/README.md`
+  - active route trees under `src/Web/StellaOps.Web/src/app/routes/`
+- Safe parallelism:
+  - each restoration-topic note can be authored independently after the shared placement rules are clear
+  - future implementation sprints can be split per topic once these shapes are accepted
+
+## Documentation Prerequisites
+- `docs/modules/ui/component-preservation-map/RESTORATION_PRIORITIES.md`
+- `docs/modules/ui/component-preservation-map/README.md`
+- `docs/modules/ui/policy-decisioning-studio/README.md`
+- `src/Web/StellaOps.Web/src/app/routes/mission-control.routes.ts`
+- `src/Web/StellaOps.Web/src/app/routes/security-risk.routes.ts`
+- `src/Web/StellaOps.Web/src/app/routes/operations.routes.ts`
+- `src/Web/StellaOps.Web/src/app/routes/releases.routes.ts`
+- `src/Web/StellaOps.Web/src/app/routes/evidence.routes.ts`
+
+## Delivery Tracker
+
+### DOCS-RTS-001 - Restoration topic index and placement rules
+Status: DONE
+Dependency: none
+Owners: Documentation author, Project Manager
+Task description:
+- Create the restoration-topics doc tree with an index and shared placement rules for stray pages, actions, drawers, and submenus.
+
+Completion criteria:
+- [x] Topic index exists.
+- [x] Placement matrix exists.
+- [x] Shared placement rules are documented.
+
+### DOCS-RTS-002 - Watchlist placement note
+Status: DONE
+Dependency: DOCS-RTS-001
+Owners: Documentation author, Product Manager
+Task description:
+- Define whether Watchlist belongs in Mission Control, Ops, or Setup, and specify how configuration versus alerts should be surfaced.
+
+Completion criteria:
+- [x] Primary owner area is defined.
+- [x] Tabs and route sketch are defined.
+- [x] Secondary placements for alerts and notifications are documented.
+
+### DOCS-RTS-003 - Reachability witnessing placement note
+Status: DONE
+Dependency: DOCS-RTS-001
+Owners: Documentation author, Product Manager
+Task description:
+- Define how witness and PoE surfaces merge into Reachability, Security, and release/evidence flows.
+
+Completion criteria:
+- [x] Primary security placement is defined.
+- [x] Witness vs PoE page/drawer ownership is documented.
+- [x] Secondary deep-link entry points are listed.
+
+### DOCS-RTS-004 - Platform Ops consolidation note
+Status: DONE
+Dependency: DOCS-RTS-001
+Owners: Documentation author, FE Architect
+Task description:
+- Define how legacy Platform Ops pages fold into the active Ops shell and where stray tools like agent fleet should live.
+
+Completion criteria:
+- [x] One-shell decision is documented.
+- [x] Grouped submenu structure is documented.
+- [x] Duplication boundaries with Setup are documented.
+
+### DOCS-RTS-005 - Triage explainability placement note
+Status: DONE
+Dependency: DOCS-RTS-001
+Owners: Documentation author, Product Manager
+Task description:
+- Define how quiet lane, AI recommendations, reason capsules, provenance, and audit bundles fit into the active triage flow.
+
+Completion criteria:
+- [x] List-level lane placement is defined.
+- [x] Detail-level explainability placement is defined.
+- [x] Audit bundles page ownership is defined.
+
+### DOCS-RTS-006 - Workflow visualization and replay placement note
+Status: DONE
+Dependency: DOCS-RTS-001
+Owners: Documentation author, FE Architect
+Task description:
+- Define where runtime workflow graphing, time travel, replay, and step-detail views live in Releases, Evidence, and workflow authoring.
+
+Completion criteria:
+- [x] Primary home in release runs is documented.
+- [x] Evidence-side and workflow-editor secondary placements are documented.
+- [x] Graph/timeline/replay tab structure is defined.
+
+### DOCS-RTS-007 - Deeper corroboration against module dossiers
+Status: DONE
+Dependency: DOCS-RTS-002
+Owners: Documentation author, Product Manager
+Task description:
+- Validate each topic shape against the owning module dossiers and convert accepted shapes into implementation sprints.
+
+Completion criteria:
+- [x] Watchlist, reachability, ops, triage, and workflow-visualization topic notes each have corroborating module-doc links.
+- [x] Accepted topic shapes are translated into implementation-ready frontend or product sprints.
+- [x] Rejected or downgraded topics are reflected back into the restoration backlog.
+
+## Execution Log
+| Date (UTC) | Update | Owner |
+| --- | --- | --- |
+| 2026-03-07 | Sprint created to shape the next restoration topics after Decisioning Studio into concrete shell/menu/tab recommendations. | Project Manager |
+| 2026-03-07 | Authored topic-shape notes for Watchlist, Reachability Witnessing, Platform Ops Consolidation, Triage Explainability Workbench, and Workflow Visualization And Replay. | Documentation author |
+| 2026-03-07 | Added corroborating module-doc links to each restoration topic note and cut implementation-ready FE sprints plus detailed UX dossiers for the accepted topics. | Documentation author |
+| 2026-03-08 | Archived after the downstream restoration delivery sprints shipped and the preservation-map corroboration pass was committed. | Project Manager |
+
+## Decisions & Risks
+- Decision: these topics should be expressed as restorations of capability into existing shells, not revivals of abandoned product brands.
+- Decision: single actions and narrow supporting UX should default to tabs, drawers, right-rail panels, or submenus instead of new top-level products.
+- Decision: completion of this docs sprint is not sufficient for product delivery; the FE sprints must still ship and verify the mounted functionality.
+- Risk: some topics, especially Watchlist and Workflow Visualization, touch more than one owning domain.
+- Mitigation: document primary ownership plus secondary entry points explicitly so implementation does not fork the capability.
+- Risk: legacy route shapes may bias the placement toward old IA instead of current Stella Ops structure.
+- Mitigation: place each topic against the active route tree first and treat legacy routes as migration aliases only.
+
+## Next Checkpoints
+- Archived 2026-03-08 after the accepted restoration topics moved into shipped delivery sprints and checked-feature notes.