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

Lesson 4 of 11 — De-duplicate discovered systems

Governance Onboarding · Source: Jira Story GOV-113 (5 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Resolve duplicate and shadow AI systems before they enter the governed record.

Why it matters

Duplicates and shadow AI inflate the estate and corrupt baselines if they enter the record.

Where this lives

Runs in the Customer AI Governance platform (components: onboarding). A comparison pass flags likely duplicates as mergeable and badges shadow systems for review; merging is a human decision. Learn teaches this read-only.

Workflow

  1. Given duplicate candidates
  2. When the list renders
  3. Then duplicates are flagged / mergeable and shadow systems are badged

Worked example

Two entries look identical but belong to different business units. What should you do?

Keep them separate — only merge true duplicates. The flag is a prompt to review, not an instruction to merge.

Acceptance criteria (authoritative — GOV-113)

Given duplicate candidates, when the list renders, then duplicates are flagged / mergeable and shadow systems are badged.

Common pitfalls

  • Merging two genuinely different systems because their names look similar.

Knowledge check

  • Scenario: Two entries look identical but belong to different business units. What should you do?
  • Look for: Keep them separate — only merge true duplicates. The flag is a prompt to review, not an instruction to merge.

Key concepts

  • duplicate flagging
  • mergeable
  • shadow badge

For the AI Tutor

  • Summary: Resolve duplicate and shadow AI systems before they enter the governed record.
  • When to use: teaching or answering questions about "de-duplicate discovered systems" during governance onboarding.
  • When NOT to use: classifying risk (that is GOV-115).
  • Key concepts: duplicate flagging, mergeable, shadow badge.

Completion criteria

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

  • Module: LEARN-MOD-001 (Governance Onboarding)
  • Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
  • Next: LEARN-LSN-005