Informational Fresh jira_story: GOV-143

Lesson 4 of 6 — System Owner scoped dashboard

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

Purpose

Give owners a focused, actionable view of their systems.

Why it matters

Owners need their slice and a fast path to act.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). The owner layout scopes to their systems/tasks; upload deep-links into the relevant task. Learn teaches this read-only.

Workflow

Given a System Owner
When they open the dashboard
Then only their systems and tasks show, and evidence upload deep-links to the task

Worked example

A System Owner uploads evidence from their dashboard. Where should it land?

Deep-linked to the specific task — not a generic inbox.

Acceptance criteria (authoritative — GOV-143)

Given a System Owner, when they open the dashboard, then only their systems and tasks show, and evidence upload deep-links to the task.

Common pitfalls

Showing the whole estate to an owner, drowning their signal.

Knowledge check

Scenario: A System Owner uploads evidence from their dashboard. Where should it land?
Look for: Deep-linked to the specific task — not a generic inbox.

Key concepts

owner scoping
deep-link to task
focused view

For the AI Tutor

Summary: Give owners a focused, actionable view of their systems.
When to use: teaching or answering questions about "system owner scoped dashboard".
When NOT to use: the read-only auditor trail (that is GOV-144).
Key concepts: owner scoping, deep-link to task, focused view.

Completion criteria

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

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