Informational Fresh jira_story: GOV-141

Lesson 2 of 6 — Governance Lead operating console

Executive Command Centre · Source: Jira Story GOV-141 (8 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Give the Lead a complete operating console.

Why it matters

The Lead drives the programme; the console surfaces what needs action.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). The Lead layout seeds all widgets and turns unowned-system warnings into assign actions. Learn teaches this read-only.

Workflow

Given a Governance Lead post-launch
When they land
Then all widgets are seeded and unowned systems nudge an assign-work action

Worked example

The Lead sees three unowned systems. What should the console let them do right there?

Assign owners — the unowned nudge converts the warning into an assign-work action.

Acceptance criteria (authoritative — GOV-141)

Given a Governance Lead post-launch, when they land, then all widgets are seeded and unowned systems nudge an assign-work action.

Common pitfalls

A console that shows status but offers no action on gaps.

Knowledge check

Scenario: The Lead sees three unowned systems. What should the console let them do right there?
Look for: Assign owners — the unowned nudge converts the warning into an assign-work action.

Key concepts

operating console
seeded widgets
unowned nudge

For the AI Tutor

Summary: Give the Lead a complete operating console.
When to use: teaching or answering questions about "governance lead operating console".
When NOT to use: executive sign-off (that is GOV-142).
Key concepts: operating console, seeded widgets, unowned nudge.

Completion criteria

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

Module: LEARN-MOD-004 (Executive Command Centre)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-024