Informational Fresh jira_story: GOV-134

Lesson 5 of 7 — Findings list and detail

Governance Workspace Core · Source: Jira Story GOV-134 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Manage findings with scoped filtering and audited edits.

Why it matters

Findings are the backlog of governance gaps; they need triage and history.

Where this lives

Runs in the Customer AI Governance platform (components: workspace). A filterable findings view with audited status/owner edits. Learn teaches this read-only.

Workflow

Given a set of findings
When they are filtered
Then results are scoped and status/owner edits persist with audit

Worked example

A finding's owner is changed but no history is recorded. What's missing?

The audit entry — every status/owner edit must persist with an audit trail.

Acceptance criteria (authoritative — GOV-134)

Given a set of findings, when they are filtered, then results are scoped and status/owner edits persist with audit.

Common pitfalls

Edits that don't write an audit entry, breaking traceability.

Knowledge check

Scenario: A finding's owner is changed but no history is recorded. What's missing?
Look for: The audit entry — every status/owner edit must persist with an audit trail.

Key concepts

findings triage
scoped filter
audited edits

For the AI Tutor

Summary: Manage findings with scoped filtering and audited edits.
When to use: teaching or answering questions about "findings list and detail".
When NOT to use: computing posture from closed work (that is GOV-135).
Key concepts: findings triage, scoped filter, audited edits.

Completion criteria

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

Module: LEARN-MOD-003 (Governance Workspace Core)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-020