stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

feat(ui): ship triage explainability workspace

Browse Source
This commit is contained in:
master
2026-03-07 21:43:55 +02:00
parent 437d26c47c
commit 8f43378317
32 changed files with 2296 additions and 259 deletions
Download Patch File Download Diff File Expand all files Collapse all files

129
docs/implplan/SPRINT_20260307_027_FE_triage_explainability_workspace.md
View File

@@ -1,129 +0,0 @@
# Sprint 20260307-027 - Triage Explainability Workspace
## Topic & Scope
- Merge the dropped triage workbench ideas into one canonical artifact workspace plus a sibling `Audit Bundles` page.
- Ship a fully usable artifact workspace with lane segmentation, detail-side explainability panels, and a working `Audit Bundles` page.
- Complete the missing triage functionality end to end so the operator can actually use quiet lane, explanation panels, and audit packaging from the active shell.
- Working directory: `src/Web/StellaOps.Web/src/app/features/triage`.
- Allowed coordination edits: `src/Web/StellaOps.Web/src/app/routes/security-risk.routes.ts`, `src/Web/StellaOps.Web/src/app/features/security-risk/`, `src/Web/StellaOps.Web/src/app/features/evidence/`, `docs/modules/ui/triage-explainability-workspace`, and `docs/modules/ui/TASKS.md`.
- Expected evidence: working lane tabs, working detail-side explainability panels, working audit-bundle flows, migrated supporting components, tests, and updated docs.
## Dependencies & Concurrency
- Depends on:
- `docs/modules/ui/triage-explainability-workspace/README.md`
- `docs/UI_GUIDE.md`
- `docs/ui-analysis/03_TRIAGE_POLICY_OPS_SCREENS.md`
- `docs/ui-analysis/05_ROUTE_SUMMARY_AND_OBSERVATIONS.md`
- `src/Web/StellaOps.Web/src/app/features/triage/triage-artifacts.component.ts`
- `src/Web/StellaOps.Web/src/app/features/triage/triage-workspace.component.ts`
- `src/Web/StellaOps.Web/src/app/features/triage/triage-audit-bundles.component.ts`
- Safe parallelism:
- route, lane, and panel contracts should freeze before FE implementation begins
- list-lane work and detail-panel work can proceed in parallel after the contract is stable
- audit-bundle page work can proceed in parallel with supporting component absorption
## Documentation Prerequisites
- `docs/modules/ui/triage-explainability-workspace/README.md`
- `docs/modules/ui/contextual-actions-patterns/README.md`
- `docs/modules/ui/restoration-topics/triage-explainability-workbench.md`
- `docs/modules/ui/component-preservation-map/RESTORATION_PRIORITIES.md`
## Delivery Tracker
### FE-TX-001 - Wire the canonical artifact workspace and route state
Status: TODO
Dependency: none
Owners: Product Manager, FE Architect
Task description:
- Implement the canonical artifact workspace route family, lane query params, panel query params, and sibling `Audit Bundles` page ownership.
- Ensure the active shell exposes the triage workspace operators should actually use.
Completion criteria:
- [ ] Canonical artifact and audit-bundle routes are active in the router.
- [ ] Lane and panel query params work in the shipped UI.
- [ ] Separate workbench brands are no longer required for triage access.
### FE-TX-002 - Ship the list-lane workflows
Status: TODO
Dependency: FE-TX-001
Owners: Developer, FE Architect
Task description:
- Implement the list-layer experience for `Active`, `Quiet Lane`, and `Needs Review`.
- Ensure row actions, bulk actions, and lane transitions are usable from the active artifact list.
Completion criteria:
- [ ] Lane tabs or segmented controls are working in the shipped UI.
- [ ] Row and bulk actions work from the artifact list.
- [ ] Quiet-lane behavior is usable as queue state, not a detached page.
### FE-TX-003 - Ship the detail-side explainability workspace
Status: TODO
Dependency: FE-TX-001
Owners: Developer, Product Manager
Task description:
- Implement artifact detail panels for AI recommendations, reason capsule, provenance, and decision history.
- Make them usable beside the central artifact summary and evidence trail instead of leaving them as unmounted workbench ideas.
Completion criteria:
- [ ] Detail-side panels render and open via the active workspace route state.
- [ ] Panel actions and return-to-context behavior work in the shipped UI.
- [ ] AI remains advisory and evidence-first in the shipped detail experience.
### FE-TX-004 - Ship the Audit Bundles page and create flow
Status: TODO
Dependency: FE-TX-001
Owners: Developer, Documentation author
Task description:
- Implement the `Audit Bundles` list, create flow, and download/verify behavior as a real sibling page.
- Ensure operators can build and retrieve audit bundles from the active triage and evidence flows.
Completion criteria:
- [ ] Bundle list and create flow are usable in the shipped UI.
- [ ] Cross-links from artifact detail and evidence open the working page.
- [ ] Audit bundles remain a visible sibling page, not a hidden modal flow.
### FE-TX-005 - Migrate supporting components and retire workbench wrappers
Status: TODO
Dependency: FE-TX-003
Owners: Developer, Documentation author
Task description:
- Migrate dropped triage components such as quiet lane workbench, AI recommendation workbench, reason capsule, snapshot viewer, unknowns list, and AI badge into the target workspace.
- Retire wrapper shells only after their preserved behavior is working in the active artifact workspace.
Completion criteria:
- [ ] Supporting components are visible in the working list or detail surfaces.
- [ ] Wrapper shells slated for retirement are no longer needed for preserved behavior.
- [ ] No preserved triage functionality depends on an orphan workbench route.
### FE-TX-006 - Verify, document, and cut over the workspace
Status: TODO
Dependency: FE-TX-004
Owners: QA, Documentation author
Task description:
- Add Playwright scenarios for list-lane navigation, detail panels, cross-links to reachability and evidence, and audit-bundle creation.
- Update triage and UI docs so the artifact workspace ships as the usable owner of these workflows.
Completion criteria:
- [ ] Verification covers lane changes, detail panels, and audit bundles.
- [ ] Cross-shell deep links are included in testing.
- [ ] Docs reflect the shipped artifact workspace and audit-bundle flows.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-07 | Sprint created to ship one artifact workspace with lane segmentation, detail-side explainability, and a sibling Audit Bundles page instead of keeping those capabilities in dropped workbench shells. | Project Manager |
## Decisions & Risks
- Decision: triage stays one workspace with contextual explainability, not multiple workbench brands.
- Decision: audit bundles remain a real page because they carry lifecycle, export, and audit semantics.
- Risk: AI recommendation UI may expand beyond advisory use and obscure evidence-first operator decisions.
- Mitigation: require explicit advisory-only copy and evidence panels in the detail contract.
- Risk: quiet-lane behavior may get over-specialized into another shell.
- Mitigation: freeze it as list segmentation plus row or bulk actions only.
- Delivery rule: this sprint is only complete when the active triage workspace provides the preserved explainability and audit workflows without depending on orphan workbench pages.
- Reference design note: `docs/modules/ui/triage-explainability-workspace/README.md`.
## Next Checkpoints
- 2026-03-08: confirm lane model, detail-side panel set, and Audit Bundles ownership.
- 2026-03-09: freeze supporting component merge matrix and route/query contract.
- 2026-03-10: finalize QA and rollout contract.