Learn · TrustedAIGov® Enterprise Knowledge Platform
Informational Fresh jira_story: GOV-220

Lesson 1 of 6 — Live SSE activity and sign-off inbox polish

Command Centre Enhancements · Source: Jira Story GOV-220 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Stream activity to the Command Centre live.

Why it matters

Real-time visibility beats manual refresh for an operating console.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). Server-Sent Events push changes to the activity feed in real time. Learn teaches this read-only.

Workflow

  1. Given a change occurs
  2. When the feed is open
  3. Then it streams to the feed live

Worked example

A task closes while the Lead is watching the feed. When do they see it?

Immediately — changes stream live via SSE, no refresh needed.

Acceptance criteria (authoritative — GOV-220)

Given a change occurs, when the feed is open, then it streams to the feed live.

Common pitfalls

  • Polling instead of streaming, adding lag and load.

Knowledge check

  • Scenario: A task closes while the Lead is watching the feed. When do they see it?
  • Look for: Immediately — changes stream live via SSE, no refresh needed.

Key concepts

  • SSE live feed
  • real-time activity
  • sign-off inbox

For the AI Tutor

  • Summary: Stream activity to the Command Centre live.
  • When to use: teaching or answering questions about "live sse activity and sign-off inbox polish".
  • When NOT to use: tuning RAG thresholds (that is GOV-221).
  • Key concepts: SSE live feed, real-time activity, sign-off inbox.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-220's acceptance criterion.

  • Module: LEARN-MOD-008 (Command Centre Enhancements)
  • Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
  • Next: LEARN-LSN-040