Informational Fresh jira_story: GOV-210

Lesson 1 of 4 — Finding and ControlIssue unification

Data Platform Hardening · Source: Jira Story GOV-210 (8 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Unify control issues and findings into one model.

Why it matters

Two issue models fragment triage; one model gives a single backlog.

Where this lives

Runs in the Customer AI Governance platform (components: platform, invariant). A Failed Test / ControlIssue is projected into the unified Workspace finding model. Learn teaches this read-only.

Workflow

Given a Failed Test issue
When it surfaces
Then it appears as a Workspace finding

Worked example

A failed control test and a workspace finding are tracked in two different places. What's the target state?

One unified model — the failed test appears as a Workspace finding.

Acceptance criteria (authoritative — GOV-210)

Given a Failed Test issue, when it surfaces, then it appears as a Workspace finding.

Common pitfalls

Leaving ControlIssue and Finding as separate silos.

Knowledge check

Scenario: A failed control test and a workspace finding are tracked in two different places. What's the target state?
Look for: One unified model — the failed test appears as a Workspace finding.

Key concepts

issue unification
single backlog
Failed Test to finding

For the AI Tutor

Summary: Unify control issues and findings into one model.
When to use: teaching or answering questions about "finding and controlissue unification".
When NOT to use: the findings UI itself (that is GOV-134).
Key concepts: issue unification, single backlog, Failed Test to finding.

Completion criteria

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

Module: LEARN-MOD-007 (Data Platform Hardening)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-036