git.stella-ops.org/docs/modules/ui/restoration-topics/triage-explainability-workbench.md

Triage Explainability Workbench

Recommendation

Do not restore the triage workbenches as separate products.

Merge them into the active triage list/detail loop, with lane controls at the list level and explainability tools in the artifact detail workspace.

Why

• QuietLaneWorkbenchComponent is really a list-state and queue-management concept.
• AiRecommendationWorkbenchComponent is a detail-side decision aid.
• ReasonCapsuleWorkbenchComponent is a provenance/explanation panel.
• TriageAuditBundlesComponent is a real supporting page, but it belongs beside triage, not as a separate workbench brand.

Primary Placement

• Menu group: Triage

Recommended submenu structure:

• Triage > Artifact Workspace
• Triage > Audit Bundles

Product Shape

Use one triage workspace with two layers:

1. List layer

• manages queues and lanes

2. Detail layer

• manages the current artifact/finding decision workspace

List-Layer Tabs

Inside Artifact Workspace, use tabs or segmented controls:

• Active
• Quiet Lane
• Needs Review

This is where the quiet-lane behavior belongs.

Detail-Layer Right Rail Or Secondary Tabs

In artifact detail, add contextual explainability surfaces:

• AI Recommendations
• Reason Capsule
• Provenance
• Decision History

These should be secondary tabs or a right-rail stack, not standalone routes.

Merge Map

Into list layer

• QuietLaneWorkbenchComponent

Into detail layer

• AiRecommendationWorkbenchComponent
• ReasonCapsuleWorkbenchComponent

Keep as sibling page

• TriageAuditBundlesComponent
  • keep as Triage > Audit Bundles
  • also deep-link from Evidence when useful

Placement For Single Actions And Stray Pages

AI suggestion apply / use VEX suggestion

• Keep inside artifact detail
• It is an action panel, not a page

Reason capsule

• Keep as expandable card or tab inside artifact detail
• It answers “why did this verdict happen?”, so it belongs next to the active decision

Provenance breadcrumb

• Keep in the detail right rail
• It is supporting context, not a route

Quiet lane recheck / extend TTL / promote

• Keep as list-row or bulk actions inside the Quiet Lane tab

Audit bundles

• Keep as a real page because it has its own list, download flow, and operator lifecycle
• Best home:
  • primary: Triage > Audit Bundles
  • secondary link: Evidence > Capsules / Exports

Suggested Route Sketch

• /triage/artifacts
• /triage/artifacts?lane=active
• /triage/artifacts?lane=quiet
• /triage/artifacts?lane=review
• /triage/artifacts/:artifactId
• /triage/artifacts/:artifactId?panel=ai
• /triage/artifacts/:artifactId?panel=reason
• /triage/artifacts/:artifactId?panel=provenance
• /triage/audit-bundles

What Not To Do

• Do not keep AI Recommendation Workbench or Reason Capsule Workbench as standalone brands.
• Do not turn every decision aid into its own route.
• Do not put quiet-lane logic on a separate page when it is fundamentally a list segmentation mode.

Detailed UX And Sprint

• Detailed UX dossier: ../triage-explainability-workspace/README.md
• Implementation sprint: ../../../docs-archived/implplan/SPRINT_20260307_027_FE_triage_explainability_workspace.md

Corroborating Inputs

• 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/routes/security-risk.routes.ts
• 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

Final Call

Restore the capability, not the workbench branding. Triage should own one artifact workspace with lane tabs on the list view and explainability panels in the detail view, plus a sibling Audit Bundles page.