noCV
CLIVE-102 · Specify live events

Render incident status text independently of severity color

Practice briefBugFoundational

Color-only status blocks hide the distinction between investigating and monitoring. Add visible status labels.

Focused work estimate
1h + prerequisites
Priority in the scenario
Medium
Engineering practice
Accessibility · State projection

Estimated field mix

  • Accessibility70%
  • Frontend30%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Project context

Fictional internal status team Harbor updates operational incident cards. Build a local event log and SSE adapter; incidents and service names are invented.

Setup prerequisites

  • Create synthetic incident revisions and a local append-only event stub.
  • Provide controllable disconnect, replay and retention fixtures.

Preceding work

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

  • Every status has text
  • Unknown status renders explicit fallback
  • Color is optional reinforcement

Implementation constraints

  • Do not infer severity from color tokens.

Verification to include

  • Render all fixture statuses
  • Render unsupported status

Deliverables

  • Status presenter and cases

Rollout and recovery

Use text-only presentation if color mapping is wrong.

Value of the work

For the engineer: Practice event projection, replay and freshness communication.

For the team: Inspect whether dashboards remain trustworthy through network interruptions.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.