Layout
Composition principles
Keep the incident queue stable while details change. Reserve the strongest emphasis for severity, customer impact, current owner, and the next required response action.
Carbon Design System / Published template
Incident Response Operations Console
An operational workspace for triaging active incidents, coordinating owners, and recording a reliable response timeline.
Prompt reference v1
Preview
Structure blueprint
A compact severity queue sits beside an incident detail workspace with ownership, service impact, timeline, and runbook actions.
Interaction
Behavior and access
Keyboard users can move through the queue and actions in a predictable order. Filters announce result counts, status changes require confirmation, and live updates do not steal focus.
Implementation
Engineering boundaries
Use server-authoritative incident state, explicit timestamps, and append-only timeline events. Virtualize only when the measured queue size requires it, and preserve accessible table semantics.
Design system
Carbon Design System token ledger
IBM's open-source design system for products and digital experiences.
Color roles
- model
- layered surfaces
- requiredRoles
- background, layer, text, interactive, support
Typography
- approach
- productive type scale
- requirements
- tabular legibility, clear information hierarchy
Spacing
- approach
- structured product grid
- baseUnitPx
- 8
Component rules
- dataTables
- Support scanning, selection, and explicit batch actions.
- notifications
- Distinguish inline, toast, and persistent operational messages.
Classification